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

From: Date: Mon, 04 Jul 2005 14:17:52 +0000
Subject: #33118 [Fbk->Opn]: Memory leak in ISAPI module after exception
References: 1  Groups: php.bugs 
Request: Send a blank email to php-bugs+get-81370@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:         IIS related
 Operating System: win32
 PHP Version:      5.*, 4.* (2005-06-20)
 New Comment:

what have the changes in the php.ini with a exception  todo ?

@sniper@php.net: Are you a programmer?

If "yes" do you know what a "handle" is? or a uninit variable is?
On my posting from 30 May i allready told you where the bug in the code
is!


Previous Comments:
------------------------------------------------------------------------

[2005-07-04 14:07:48] sniper@php.net

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!


------------------------------------------------------------------------

[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..


------------------------------------------------------------------------

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


Thread (16 messages)

« previous php.bugs (#81370) next »