ID: 16325
Comment by: jakub at icewarp dot com
Reported By: mail-php dot net at kimihia dot org dot nz
Status: Verified
Bug Type: IIS related
Operating System: Windows 2000 Server
PHP Version: 4.3.2RC1
New Comment:
Yes it's exactly the same problem as bug #23331. I'm the writer of it.
If you need any info I'd like to help. I wrote my own web server so I
can test anything... I'd like that to be solved at last. It's been
there since the beginning. A little tool generating X hits per second
proves it.
Cheers
J
Previous Comments:
------------------------------------------------------------------------
[2003-08-15 08:48:58] [EMAIL PROTECTED]
Isn't this same as bug #23331 is about? (which seems to have a bit more
analysis of the problem too)
------------------------------------------------------------------------
[2003-06-09 03:47:28] [EMAIL PROTECTED]
Sorry for the spam.
Who are code writers for IIS related stuff?
I'm supposed to be the guy who examines all these IIS related bugs, but
I've never had to modify the code.
------------------------------------------------------------------------
[2003-06-09 03:45:08] mail-php dot net at kimihia dot org dot nz
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.
------------------------------------------------------------------------
[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-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
------------------------------------------------------------------------
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
