php-fastcgi and memory leaks

Phillip B Oldham phill at
Mon Mar 31 16:47:07 MSD 2008

Grzegorz Nosek wrote:
> On Mon, Mar 31, 2008 at 01:28:22PM +0100, Phillip B Oldham wrote:
> Now that is strange. The parent process doesn't do almost anything.
> Maybe running under valgrind will provide some insight (though it is
> *SLOW*).
Actually, thats my error - they were jumping around a lot in `top`. `ps 
auxf` shows the parent process holding steady at 1.7%.
> In theory, no. In practice, who knows. It is PHP, after all ;)
> AFAIK, there is no possibility (apart from very nasty hacks) for
> extensions to cause _gradual_ increase in parent's memory usage.
> Does the parent process grow at the same rate?
Again, sorry. No, it stays steady. Just the children grow steadily.
> Is php-fcgi the only process that exhibits this behaviour? Maybe there's
> something wrong with your system libraries?
Nope, just PHP.
> Frankly, I have no idea. If you can reproduce the problem in a test
> environment, try running php under "valgrind --leak-check=full"
Thanks, I'll look into doing that. I've not used valgrind before, so 
should be fun!


*Phillip B Oldham*
The Activity People
phill at <mailto:phill at>



This e-mail and its attachments are intended for the above named 
recipient(s) only and may be confidential. If they have come to you in 
error, please reply to this e-mail and highlight the error. No action 
should be taken regarding content, nor must you copy or show them to anyone.

This e-mail has been created in the knowledge that Internet e-mail is 
not a 100% secure communications medium, and we have taken steps to 
ensure that this e-mail and attachments are free from any virus. We must 
advise that in keeping with good computing practice the recipient should 
ensure they are completely virus free, and that you understand and 
observe the lack of security when e-mailing us.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: phill.vcf
Type: text/x-vcard
Size: 272 bytes
Desc: not available
URL: <>

More information about the nginx mailing list