ID:               23331
 Updated by:       [EMAIL PROTECTED]
 Reported By:      jakub at icewarp dot com
-Status:           Open
+Status:           Feedback
 Bug Type:         IIS related
 Operating System: win32
 PHP Version:      4.3.3RC4-dev
 New Comment:

You have some extensions loaded in php.ini, right?
Which ones are those? What if you don't load them?



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

[2003-08-18 09:24:49] jakub at icewarp dot com

The problem is still there. Nothing has changed. 
I performed the same 2 tests. 

1. LoadLibrary and FreeLibrary - 200 cycles = 50MB leak
2. HttpExtensionProc - 1000 calls = 500kB leak

Please, let me know how can I help.
Jakub

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

[2003-08-15 08:48:14] [EMAIL PROTECTED]

btw. Isn't this same as bug #16325 ??


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

[2003-08-15 08:31:35] [EMAIL PROTECTED]

Please try using this CVS snapshot:

  http://snaps.php.net/php4-STABLE-latest.tar.gz
 
For Windows:
 
  http://snaps.php.net/win32/php4-win32-STABLE-latest.zip



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

[2003-05-05 03:20:29] jakub at icewarp dot com

Still the same. Btw. what I testing now is not the COM object issue but
simple HttpExtension call which leaks the memory. Each call to the
ISAPI module leaks some memory. Tell me. Thanks

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

[2003-05-03 10:22:59] jakub at icewarp dot com

I was wrong about the [EMAIL PROTECTED] it is called by Windows
automatically. However I have found for instance this.
If you load the ISAPI module and free it in a cycle again it does not
free the memory.
for ($i=0;$i<1000;$i++)
{
  lh = loadlibrary("...isapi.dll");
  freelibrary(lh);
}
After 200 cycles the process consumes 50MB. I don't think that should
happen. What is wrong?

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

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/23331

-- 
Edit this bug report at http://bugs.php.net/?id=23331&edit=1

Reply via email to