#33118 [Opn->Fbk]: Memory leak in ISAPI module after exception

ID: 33118 Updated by: sniper@php.net Reported By: T dot Hauck at janaserver dot de -Status: Open +Status: Feedback Bug Type: IIS related Operating System: win32 PHP Version: 5.*, 4.* (2005-06-20) New Comment: 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 Previous Comments: ------------------------------------------------------------------------ [2005-06-13 12:19:04] T dot Hauck at janaserver dot de Can i post you last answer in the commen news media? Why is there than a ISAPI Modul ? And why is there a "apache" modul, if cgi is recommended? ------------------------------------------------------------------------ [2005-06-13 11:09:14] sniper@php.net Using the ISAPI module isn't recommended anyway, fastcgi is much more stable.. ------------------------------------------------------------------------ [2005-06-05 20:04:52] thomas at kaiserauer dot org Memory leak still persists in version 5.0.5 dev. from Jun 05, 2005 16:30 GMT!! Currently I'm forced to run PHP as Fast-CGI because running as ISAPI does not work because of this problem. I'm looking forward to it's bugfix! ------------------------------------------------------------------------ [2005-05-30 10:48:05] 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-05-27 09:03:27] sniper@php.net See also bug #32475 ------------------------------------------------------------------------ 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/33118 -- Edit this bug report at http://bugs.php.net/?id=33118&edit=1