Bug #11676 Updated: A few apache children consume all memory and CPU.

ID: 11676 Updated by: rodrigo@labhpardini.com.br Reported By: valerio@wnet.it Status: Closed Bug Type: Scripting Engine problem Operating System: linux 2.4.5 i386 PHP Version: 4.0 Latest CVS (2001-06-25) New Comment: Valerio, did you happen to solve the bug? I'm running through practically the same bug. Besides that I'm getting a lot of Segmentation faults in error_log. I've been able to GDB some of child httpd processes before they died and it happened with some PHP stuff too as detailed in: http://marc.theaimsgroup.com/?l=apache-httpd-users&m=101482626416049&w=2 I'm anxious to know in what position this case is. Previous Comments: ------------------------------------------------------------------------ [2002-01-02 15:08:37] valerio@wnet.it Ops...guess i missed the mail with the "feedback" status.. I will check as soon as i install php 4.1 (should be tomorrow if all goes well...). Don't close this one since many were experiencing the same problem than me... i'll let you know! ------------------------------------------------------------------------ [2002-01-02 13:56:38] lobbin@php.net No feedback. Closing. ------------------------------------------------------------------------ [2001-12-12 08:20:11] yohgaki@php.net Status = feedback ------------------------------------------------------------------------ [2001-12-12 08:19:47] yohgaki@php.net Could you try 4.1.0? see if it helps? ------------------------------------------------------------------------ [2001-08-19 05:31:51] valerio@wnet.it There's only one issue... how can I determine which script was running on the processes that i find stuck? In the meanwhile i installed the Zend Optimizer on the server, and the problem seems to happen VERY less frequently... i know this is nearly no help at all, but I'm doing all I can. Anyway, i see some other guy had my same problem... ------------------------------------------------------------------------ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at http://bugs.php.net/11676 -- Edit this bug report at http://bugs.php.net/?id=11676&edit=1