ID: 31558 Updated by: [EMAIL PROTECTED] Reported By: jdw at nearlyfreespeech dot net -Status: Open +Status: Feedback Bug Type: Apache related Operating System: FreeBSD PHP Version: 4CVS-2005-01-21
Previous Comments: ------------------------------------------------------------------------ [2005-05-18 00:49:54] jdw at nearlyfreespeech dot net Interestingly, there is some evidence that this bug may be either mitigated or fixed in 4.3.11. We have also switched to using more shared modules, so it is also possible that the leak still exists, but is related to a specific extension that is now not being loaded by the "core" apache process (causing the leak not to accrue across generations). It may be possible for us to investigate that possibility and provide more information to rule it in or out. ------------------------------------------------------------------------ [2005-05-18 00:16:04] [EMAIL PROTECTED] Yes it would. We're currently focused on PHP 5 development, and if you really want stuff get fixed: Try the snapshot. (if this happens in PHP 5.1-dev too, it's more likely to be fixed also in the PHP_4_3 branch..) ------------------------------------------------------------------------ [2005-05-17 14:11:36] jdw at nearlyfreespeech dot net Um, as this is a PHP 4 bug, trying a PHP 5 snapshot would not seem to be appropriate. ------------------------------------------------------------------------ [2005-05-17 12:02:53] [EMAIL PROTECTED] Please try using this CVS snapshot: http://snaps.php.net/php5-latest.tar.gz For Windows: http://snaps.php.net/win32/php5-win32-latest.zip ------------------------------------------------------------------------ [2005-01-22 06:55:13] jdw at nearlyfreespeech dot net I also looked at the source code. Without a detailed understanding of zend_hash_*, it isn't clear that all the per_dir_info malloc() cases in sapi/apache/mod_php4.c (particularly php_value_handler_ex() ) are being properly freed by php_destroy_per_dir_info(). That's just a WAG, but it might be something to look into as a possible cause. ------------------------------------------------------------------------ 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/31558 -- Edit this bug report at http://bugs.php.net/?id=31558&edit=1
