Well...this is why we have multitasking operating systems - so that even when one process wants to consume 100% of the CPU, other processes still get a look in.
The only situation in which a process could starve another of CPU is when one or more of its threads runs with raised priority. But if that's really the case, the whole machine will be completely unusable - if a high priority thread is hogging the CPU then nothing else on the machine will run at all. (With the possible exception of Task Manager, which runs with high priority, presumably to give you a way of recovering from precisely this situation...) So unless the machine appears to be almost completely frozen, I don't think this will be the problem. -- Ian Griffiths DevelopMentor ----- Original Message ----- From: "Stefan Holdermans" <[EMAIL PROTECTED]> > Lidor wrote: > > > I don't know if this is relevant but I try to kill the process when it is > > stuck on an infinite loop and consumes ~100% CPU. > > Seems relevant to me. When another process is consuming 100% --- or almost > 100 % --- off your CPU-resources, how is your coding going to be run!? You can read messages from the Advanced DOTNET archive, unsubscribe from Advanced DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
