ID: 16325
User updated by: mail-php dot net at kimihia dot org dot nz
Reported By: mail-php dot net at kimihia dot org dot nz
-Status: No Feedback
+Status: Open
Bug Type: IIS related
Operating System: Windows 2000 Server
PHP Version: 4.3.2RC1
New Comment:
I still watch this bug ocassionally, but as I no longer have access to
the Windows 2000 Server it is little use.
When I left, and when I stepped someone else through it recently when
they upgraded, there were using ISAPI for a page that needed to set
cookies. Due to the memory problems (which only appear when multiple
PHP processes are running) it is not used throughout the entire site.
Previous Comments:
------------------------------------------------------------------------
[2003-06-07 06:32:04] nicolai at petri dot cc
Same shit still...
Why not fix the bug instead of closing this pr constantly ?
IIS + PHP + ISAPI is a no-go for all my testcases.. Is anybody actually
using this successfully ?
------------------------------------------------------------------------
[2003-05-30 08:43:20] [EMAIL PROTECTED]
No feedback from the ORIGINAL bug submitter.
------------------------------------------------------------------------
[2003-05-29 15:03:27] [EMAIL PROTECTED]
reopen, there has been feedback.
------------------------------------------------------------------------
[2003-05-29 14:52:26] fer at onplaza dot com
Same as others, normally HOSTDLL.EXE grows between 1-2 Mb per request.
I've stopped all the rest of services, created a phpinfo.php whith only
the named function and a phpinfo.htm; both in the same directory, and
if only happens when calling the .php extension page.
That's why I think that in this case we are not in front of an IIS
problem. Looks like a big leak of memory that in some cases php is
unable to handle
This is my 6'th year using PHP.
Fer
------------------------------------------------------------------------
[2003-04-21 07:25:24] nicolai at petri dot cc
This happens also for me with both php 4.3.1 and 4.3.2 RC1.
It also happens even if I don�t load any extensions, so the leak seems
to be in the core php stuff. I tested with my own pages and phpinfo()
pages. Each hit generates 2-3 Mb. of mem. leak.
Another (maybe related) observation i did, was that when I run with
mssql extension and use pconnect calls.. phpinfo() always shows 0
connections and 0 persistent connections. So maybe php cannot locate
it's runtime datastructures and re-allocates them on each hit ?
I cannot compile php from sources. But if anyone can point me to a
debug build I can try that with memleak detection on.
Best regards,
Nicolai Petri
------------------------------------------------------------------------
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/16325
--
Edit this bug report at http://bugs.php.net/?id=16325&edit=1
