Date: Fri, 16 Feb 2007 21:02:25 +0100 From: =?ISO-8859-2?Q?Nagy_L=E1szl=F3_Zsolt?= <nagylzs@freemail.hu> To: Sergey Zaharchenko <doublef-ctm@yandex.ru>, freebsd-questions@freebsd.org Subject: Re: Invisible process killing the CPU Message-ID: <45D60DD1.6050208@freemail.hu> In-Reply-To: <20070216192847.GA8358@shark.localdomain> References: <45D5D042.4000202@designaproduct.biz> <45D5D81E.1080700@joeholden.co.uk> <45D5E1BA.6010504@freemail.hu> <20070216192503.GA7827@shark.localdomain> <20070216192847.GA8358@shark.localdomain>
next in thread | previous in thread | raw e-mail | index | archive | help
> 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... > Yessssssssssssss! 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!!!!!
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?45D60DD1.6050208>