#18523 [Opn->Fbk]: httpd Memory consumption with new PHP

From: Date: Mon, 29 Jul 2002 23:50:29 +0000
Subject: #18523 [Opn->Fbk]: httpd Memory consumption with new PHP
References: 1  Groups: php.bugs 
Request: Send a blank email to php-bugs+get-15529@lists.php.net to get a copy of this message
ID: 18523 Updated by: sniper@php.net Reported By: tomki@alink.net -Status: Open +Status: Feedback Bug Type: Apache related Operating System: BSDI 4.1 PHP Version: 4.2.2 New Comment: You're actually NOT supposed to compile with shared c-client. Just let us know WHAT the error is when you try to compile with the static c-client. Previous Comments: ------------------------------------------------------------------------ [2002-07-29 14:59:40] tomki@alink.net msopacua: It's actually not GD. It's IMAP. Initially I attempted to use the latest RC2, and began seeign this problem.. I've tried the 2000c and 2001a since, but no dice. I've tried it with nothing but IMAP + mysql + apxs.. within a minute there are btwn 3 and 5 httpd processes consuming 98% of the CPU. A problem I'm having that may be related?? The UW imapd compilation does not generate .so libraries.. and php complains after the MAKE if the dynamic libraries are not present. I can make them manually in the c-client directory, with 'gcc -shared -o c-client.so *.o'.. At that point the PHP compile does not complain.. ------------------------------------------------------------------------ [2002-07-27 20:44:33] msopacua@idg.nl I'm pretty sure this is a dupe of: http://bugs.php.net/bug.php?id=14870 tomki: Can you strip the GD stuff? Instead of SIGUSR1 use SIGHUP and tail the error log, looking for "child [pid] still didn't exit" errors. It's SOME dl issue with BSDi, but I still haven't figure it out either. As a side note: all this goes away when you compile as a static module. If you're tight on memory, be sure to strip httpd manually after install, saves a meg or so, depending on the modules of course. ------------------------------------------------------------------------ [2002-07-24 19:36:59] sniper@php.net First try with ONLY --with-apxs option. And that works, then add the options you had one by one and see after which one it starts to do this. Also, try this snapshot: http://snaps.php.net/php4-latest.tar.gz ------------------------------------------------------------------------ [2002-07-24 01:57:14] tomki@alink.net Apache 1.3.26 with mod_ssl is the webserver. DSO support. I have PHP 4.1.2 configured like so, which does not cause this memory problem: './configure --with-mysql --with-apxs=/usr/local/web/apache/bin/apxs' I currently have configured PHP 4.2.2 like so: ./configure --with-regex=php --enable-memory-limit --with-mysql=/usr/local/mysql --with-imap=../imap-2002.RC2 --with-imap-ssl --with-ttf --with-gd --enable-ftp --with-bz2=/usr --with-zlib --with-openssl --with-apxs=/usr/local/web/apache/bin/apxs --with-freetype-dir=/usr/local --enable-gd-native-ttf --with-jpeg-dir=/usr --with-png-dir=/usr --with-pear --with-mm and as soon as I install the new libphp4.so, and restart apache... the new httpd processes dominate all the CPU time. Not hideously badly, but enough so I can't let it continue. The load goes to 7 or 8 and stays there. The issue goes away when the older module is replaced. There are no compile or make errors printed that I've noticed. What can I do to resolve this? Is this a known problem with a certain combination of modules? Thanks ------------------------------------------------------------------------ -- Edit this bug report at http://bugs.php.net/?id=18523&edit=1

« previous php.bugs (#15529) next »