System Idle Process

Hello!

First of all: This question I am asking not because I have a specific
problem, but purely because I want to know it.

The question is: What is the story behind the mystical "System Idle Process"
(PID:0)? According to TaskManager, this process uses some memory (seem to be
always 28k)and owns two threads. It is not possible to attach a debugger to
the process. I was not able to get a ProcessHandle via OpenProcess(0).

Can you tell me something about this?



GP


.

Relevant Pages

  • Re: Memory Issue
    ... If I let the app run for 20 minutes it runs out of memory. ... Unfortunately after you attach a debugger 20 minutes might turn into 20,000 minutes. ... Get a debugger or other performance tool, attach it and let the process run. ...
    (comp.lang.java.help)
  • RE: Memory growth halts with use of Profiler - bug in .NET services?
    ... unless I attach a debugger to it. ... application instead of as a service, I have no memory problems at all. ... I'll try the SOS debugger and also the CLRProfiler, ... This is basically the manual version of what CLRProfiler does; ...
    (microsoft.public.dotnet.framework.performance)
  • Re[4]: Protecting code and data in Windows
    ... DE> How about using something like VirtualProtectExand set the memory storing ... This approach could be interesting to "protect" from malicious code ... So the first problem to soluce will be to avoid such a debugger ... to attach to our critical process. ...
    (SecProg)
  • Unable to boot with SiS ATA chipsets (Re: Unable to boot on ECS K7S5A)
    ... has SiS vendor ID as an ATA controller. ... avail memory = 239845376 ... device_attach: ata0 attach returned 6 ... miibus0: on dc0 ...
    (freebsd-current)
  • Re: MyString Class
    ... > I compiled your program and run it under the debugger. ... > The first crash happens in ... ... > memory is flawed. ... First bug fixed. ...
    (comp.lang.cpp)