7 May
2010
7 May
'10
9:57 a.m.
On 30 Mar 2010, at 20:18, Nicholas Cole wrote:
[…] Once it is triggered, any new process starts eating up the CPU, no matter what it is, and killing it in the task manager doesn't reduce the CPU load. That's why I find this bug so odd...
Then just run ‘sample’ on a new process.
Most likely some OS service has “gone down” and is what is causing the problem. Getting a stack trace (from sample) will likely show what OS service the task is using.