#33118 [Fbk->Opn]: Memory leak in ISAPI modul after exception
| From: | T dot Hauck at janaserver dot de | Date: | Tue, 24 May 2005 09:48:34 +0000 |
| Subject: | #33118 [Fbk->Opn]: Memory leak in ISAPI modul after exception | ||
| References: | 1 | Groups: | php.bugs |
| Request: | Send a blank email to php-bugs+get-79433@lists.php.net to get a copy of this message | ||
ID: 33118
User updated by: T dot Hauck at janaserver dot de
Reported By: T dot Hauck at janaserver dot de
-Status: Feedback
+Status: Open
Bug Type: Reproducible crash
Operating System: Windows 2000 / XP / All
PHP Version: 5.0.4, 4.3.11
New Comment:
Memeory leak still exist in the Snap Shot of Version 5.0.5 dev.
The Bugreport was original reported for Version 4.3.11 and not for
Version 5.0.4 !
Previous Comments:
------------------------------------------------------------------------
[2005-05-24 10:00:56] sniper@php.net
Please try using this CVS snapshot:
http://snaps.php.net/php5-STABLE-latest.tar.gz
For Windows:
http://snaps.php.net/win32/php5.0-win32-latest.zip
------------------------------------------------------------------------
[2005-05-24 09:40:32] T dot Hauck at janaserver dot de
Description:
------------
In each call to the HttpExtensionProc in the ISAPI Modul of PHP a
Windows exception 0x000006A6 is raised. I debuged it back to the that
line of sourcecode: DeregisterEventSource(PW32G(log_source));
Line 64 in file wsyslog.c
After stepping into that line the exception 0x000006A6 is raised.
The Stackframe looks like that:
php4ts_debug.dll!closelog() Line 64
php4ts_debug.dll!zm_deactivate_syslog (....) Line 125
php4ts_debug.dll!zm_deactivate_basic (....) Line 1243
php4ts_debug.dll!modul_registry_cleanup (....) Line 1168
php4ts_debug.dll!zend_hash_apply (....) Line 701
php4ts_debug.dll!zend_deactivate_moduls (....) Line 678
php4ts_debug.dll!php_request_shutdown (....) Line 982
php4isapi.dll!HttpExtensionProc (....) Line 899
I have a screenshot avalible with all the details of the stackframe.
In normal operation mode, the only sign will be only a memory leak.
The problem was NOT pressent in version 4.3.10.
But PHP version 5.0.4 has the same problem.
------------------------------------------------------------------------
--
Edit this bug report at http://bugs.php.net/?id=33118&edit=1