ID: 20665 Updated by: [EMAIL PROTECTED] Reported By: [EMAIL PROTECTED] -Status: Open +Status: Feedback Bug Type: Apache related Operating System: BSD/OS 4.2 PHP Version: 4.3.0RC1 New Comment:
As a security procution Apache does not write core files, in order to make it do so you must tell it where to write core files using: CoreDumpDirectory /tmp. In debug builds Zend will segfault if emalloc() fails to allocate memory. Also, could you please include the list of extensions you've compiled your PHP with (put config.nice online somewhere?). Previous Comments: ------------------------------------------------------------------------ [2002-11-28 06:34:38] [EMAIL PROTECTED] Yes, it does put out the scriptname, with the mem leaks -it's always the same script, which is nothing more than a static file which echo's the current timestamp into 8 different places for banners - that's why it doesn't make sence. However - when an emalloc call fails, it doesn't output the scriptname nor the c file, which called the emalloc. It only happens a few times a day, so the cause could be the memory leaks or it could be a script which isn't requested too much. I see a SIGSEV afterwards, but no core dump and it's not like I can startup Apache from gdb and request a certain file to reproduce it, since I have no idea where to look. I will recheck settings to make it dump core. What's also strange is that these leaks only get reported on a SIGHUP. Through the entire error log, there are no other leak reports. This would suggest something in the SIGCHILD and therefore the shutdown handler. ------------------------------------------------------------------------ [2002-11-27 17:03:22] [EMAIL PROTECTED] The code that reports memory leaks also outputs PHP script name where the leak had occured. I am not sure if this was part of the RC1, so just to be sure, try RC2 and make sure to clear the error log so that old messages do not get confused for new ones. ------------------------------------------------------------------------ [2002-11-27 03:05:26] [EMAIL PROTECTED] Yep apache. ------------------------------------------------------------------------ [2002-11-26 20:19:13] [EMAIL PROTECTED] Was this with Apache? Please reclassify if so. This is NOT "Performance problem".. ------------------------------------------------------------------------ [2002-11-26 19:47:48] [EMAIL PROTECTED] Running 4.3RC1 in production, I see a returning problem, for the allocation of 129 bytes. Since no executed file is being reported it's hard for me to track down which is the cause. Additionally, on logrotation and a SIGHUP, there are leaks being reported, broken down to: /home/mdev/_src/php-4.3.0RC1/Zend/zend_opcode.c(295) : Freeing 0x082F6024 (7200 bytes) Zend/zend_language_scanner.c(4365) : Freeing 0x082E2824 (50 bytes) Last leak repeated 112 times Zend/zend_language_scanner.c(4450) : Freeing 0x082DFAE4 (4 bytes)Last leak repeated 2 times /home/mdev/_src/php-4.3.0RC1/Zend/zend_hash.c(262) : Freeing 0x082DE324 (100 bytes) Last leak repeated 76 times Zend/zend_language_scanner.c(3060) : Freeing 0x082E01A4 (84 bytes) /home/mdev/_src/php-4.3.0RC1/Zend/zend_execute.c(478) : Freeing 0x082DF7A4 (12 bytes) /home/mdev/_src/php-4.3.0RC1/Zend/zend_hash.c(406) : Freeing 0x082E2124 (35 bytes) etc. Full log here: http://melvyn.idg.nl/php43/leaks.log I stripped the script= part as it doesn't make any sence. Note that this is the only point where these leaks are reported. ------------------------------------------------------------------------ -- Edit this bug report at http://bugs.php.net/?id=20665&edit=1
