ID: 38613 Comment by: adam-phpbugs at adam dot gs Reported By: neil at fissure dot net Status: No Feedback Bug Type: SNMP related Operating System: CentOS release 4.3 PHP Version: 5.1.5 New Comment:
Hello, This bug is still in PHP-5.2.9 and PHP-5.3.0. I can confirm that disabling snmp_shutdown() in PHP_MSHUTDOWN_FUNCTION(snmp) corrects the issue with no apparent side effects. Previous Comments: ------------------------------------------------------------------------ [2008-07-29 09:57:51] cinek at xo dot pl This bug is still in PHP 5.2.6 Works perfectly with commented line, in the PHP_MSHUTDOWN_FUNCTION(snmp) function of: ext/snmp/snmp.c ------------------------------------------------------------------------ [2007-04-10 01:00:00] php-bugs at lists dot php dot net No feedback was provided for this bug for over a week, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open". ------------------------------------------------------------------------ [2007-04-02 22:07:29] sni...@php.net Please try using this CVS snapshot: http://snaps.php.net/php5.2-latest.tar.gz For Windows: http://snaps.php.net/win32/php5.2-win32-latest.zip ------------------------------------------------------------------------ [2006-08-30 17:52:38] neil at fissure dot net Commenting out this line, in the PHP_MSHUTDOWN_FUNCTION(snmp) function of: src/web/php-5.1.6/ext/snmp/snmp.c diff snmp.c snmp.c.orig 223c223 < /* snmp_shutdown("snmpapp"); */ --- > snmp_shutdown("snmpapp"); but possibly at the risk of re-introducing the memory leak it was added to combat? ------------------------------------------------------------------------ [2006-08-30 16:56:20] neil at fissure dot net I figured it was a PHP issue as it matched a similar bug report which was acknowledged to be due to a code change in PHP. In that bug, sniper AT php.net, who make the change, said they were using Apache 2 (and would test with Apache 1.x if they got a chance). So I'm figuring this issue lies with PHP and Apache 1.x I'm happy to do any requested testing/diagnostics if you can give me some pointers. I'm getting the same errors as in bug 32680 (which was acknowledged to be a PHP issue, not say an Apache issue). Thanks for your time, Neil. ------------------------------------------------------------------------ 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/38613 -- Edit this bug report at http://bugs.php.net/?id=38613&edit=1
