php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login

go to bug id or search bugs for

Bug #33118 Memory leak in ISAPI module after exception
Submitted: 2005-05-24 09:40 UTC Modified: 2005-09-21 01:00 UTC
Votes:36
Avg. Score:4.9 ± 0.3
Reproduced:35 of 35 (100.0%)
Same Version:34 (97.1%)
Same OS:35 (100.0%)
From: T dot Hauck at janaserver dot de Assigned:
Status: No Feedback Package: IIS related
PHP Version: 5.*, 4.* (2005-06-20) OS: win32
Private report: No CVE-ID: None
View Developer Edit
Welcome! If you don't have a Git account, you can't do anything here.
If you reported this bug, you can edit this bug over here.
(description)
Block user comment
Status: Assign to:
Package:
Bug Type:
Summary:
From: T dot Hauck at janaserver dot de
New email:
PHP Version: OS:

 

 [2005-05-24 09:40 UTC] 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.

Patches

Pull Requests

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2005-05-27 09:03 UTC] sniper@php.net 
See also bug #32475
 [2005-05-30 10:48 UTC] T dot Hauck at janaserver dot de 
i don't know if bug #32475 is relatet!

But when is the function "openlog" in the file "wsyslog" is called? Not as far as i know! This function makes the handle that later will be used in the function "closelog". As far as i can see this, this handle is never be initalised, and by calling the "closelog" function this "wild" handle is used to call the "DeregisterEventSource" handle, what generates than the Exeption. If i step with the debugger over the "DeregisterEventSource" function everything works fine !
 [2005-09-13 11:09 UTC] sniper@php.net 
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-09-21 01:00 UTC] 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".
 
PHP Copyright © 2001-2024 The PHP Group
All rights reserved. 		Last updated: Sat Dec 21 13:01:31 2024 UTC