ID: 23331
Comment by: egarcia at egm dot as
Reported By: jakub at icewarp dot com
Status: Open
Bug Type: IIS related
Operating System: win32
PHP Version: 4.3.3RC5-dev
New Comment:
I have a simmilar trouble, with IIS & PHP memory leak.
I have a small program that connect to MySQL and MSSQLServer.
This small program open a MySQL and MS SQL Server connection, then it
does some querys to pass data from MSSQL to MySQL. When it finishes,
the dllhost.exe associated to the IWAM_USER have consumed 1.4GB of
virtual memory and doesn´t release. I have to kill this process to
free the resources.
The program is very simple, makes a query on MSSQL and row by row build
an insert into MySQL.
Previous Comments:
------------------------------------------------------------------------
[2003-08-21 10:52:24] jakub at icewarp dot com
I can send you a small tool I made. It connects to any web server and
issues the GET /... HTTP command in a given cycle and given number of
threads. You can test it easily with it. It's very handy. Just let me
know.
------------------------------------------------------------------------
[2003-08-18 09:42:43] jakub at icewarp dot com
That's what I thought of too so I removed all extensions and the
results I posted are without any extensions.
------------------------------------------------------------------------
[2003-08-18 09:31:14] [EMAIL PROTECTED]
You have some extensions loaded in php.ini, right?
Which ones are those? What if you don't load them?
------------------------------------------------------------------------
[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 ??
------------------------------------------------------------------------
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
