Invisible process killing the CPU

Nagy László Zsolt nagylzs at
Fri Feb 16 20:02:33 UTC 2007

> Ouch, that's pages freed by exiting processes, not process forks (gotta
> get some sleep). Anyway, if this is persistent, then some processes are
> exiting all the time, and they have to get created somehow, so the
> scenario is the same...
That was it! Thank you so much! :-)

There was a program that forked another in a loop. The forked program 
was working for days, but now it is throwing an error. You were right. 
The parent process was starting the child process at an incredibly rate. 
And you were also right in that, since the child processes were running 
only for some msec, they where not recognized by top and so they were 
not shown.

You are a genious! :-) Thank you!!!!!

More information about the freebsd-questions mailing list