ID: 16325
Updated by: [email]sniper@php.net[/email]
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:

Isn't this same as bug #23331 is about? (which seems to have a bit more
analysis of the problem too)



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

[2003-06-09 03:47:28] [email]kimihia@php.net[/email]

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

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

[2002-03-27 23:06:39] mail-php dot net at kimihia dot org dot nz

The setup:

IIS5 has an ISAPI application mapping to php4isapi.dll

Steps to reproduce:

- Start IIS
- Generate heavy load (~40+ hits / second)
- Watch DLLHOST in the Task Manager. It takes more and more memory (40
- 45MB)
- PHP error log begins reporting spurious errors (the page has no
errors, but under heavy load it starts complaining about duplicate
function definitions) Bug: #13324
- IIS stops serving PHP files but still serves static content

DLLHOST disappears from the task list at this point.

Other times it may begin taking 100% CPU and need to be terminated by
hand.

Killing DLLHOST usually causes it to be restarted and requests continue
being served. Otherwise you may end up alternating between the two
errors on bug #13324.

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


--
Edit this bug report at [url]http://bugs.php.net/?id=16325&edit=1[/url]