#33118 [Opn->Fbk]: Memory leak in ISAPI module after exception
| From: | sniper@php.net | Date: | Mon, 04 Jul 2005 12:07:49 +0000 |
| Subject: | #33118 [Opn->Fbk]: Memory leak in ISAPI module after exception | ||
| References: | 1 | Groups: | php.bugs |
| Request: | Send a blank email to php-bugs+get-81363@lists.php.net to get a copy of this message | ||
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:
What changes have you made to php.ini (compared to whatever php.ini-*
you used as template)
note: DO NOT paste the whole php.ini file here, just the changes!
Previous Comments:
------------------------------------------------------------------------
[2005-07-04 08:44:15] T dot Hauck at janaserver dot de
Error still exist.
------------------------------------------------------------------------
[2005-07-04 01:05:50] 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-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!
------------------------------------------------------------------------
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