ID: 38111
Updated by: paj...@php.net
Reported By: svendavidh at hotmail dot com
Status: Feedback
Bug Type: IIS related
Operating System: Windows Server 2003 Std. Ed. R2
PHP Version: 5.2.8
Assigned To: pajoye
New Comment:
Yes, a simple phpinfo and then restart IIS is all it need to crash.
(Note: I am using IIS on Vista 64, and have to create a new
Application
Pool and then enable 32-bit application)
As for why we stick with ISAPI:
"1. We have an php extension for handling proprietary protocol and it
has significant overhead on startup. We will try FastCGI, but in the
meantime we keep in in ISAPI mode so that it won't get loaded and
unloaded frequently."
That should not be a problem at all.
"2. FastCGI could be way better, but ISAPI is still a legitimate mode
for PHP. So I am a bit surprise to see you persuade others to use
FastCGI as a way to avoid this bug. Well of course, use Apache or Linux
also "fix" this problem as well."
Nobody maintains it and it is likely to be dropped. It was never stable
and it is very unlikely that we will fix it any time soon. It is also
the recommend way, according to the IIS team (and I work with them on
that).
"BTW, FastCGI is an excellent idea to make PHP more stable. But I am
worry it becomes a way to hide all the thread-safe, memory leak issues
and allow them not being fixed properly."
There is no tread safety issue with fastcgi because this SAPI is not
threaded (like ISAPI or some apache2 sapi). I do not understand your
point with the memory leaks.
Previous Comments:
[2009-02-10 20:55:56] tser at deltacontrols dot com
Just to clarify again.
The crash could be duplicated without any extension loaded, our own
extension is not loaded neither.
[2009-02-10 20:52:28] tser at deltacontrols dot com
Yes, a simple phpinfo and then restart IIS is all it need to crash.
(Note: I am using IIS on Vista 64, and have to create a new Application
Pool and then enable 32-bit application)
As for why we stick with ISAPI:
1. We have an php extension for handling proprietary protocol and it
has significant overhead on startup. We will try FastCGI, but in the
meantime we keep in in ISAPI mode so that it won't get loaded and
unloaded frequently.
2. FastCGI could be way better, but ISAPI is still a legitimate mode
for PHP. So I am a bit surprise to see you persuade others to use
FastCGI as a way to avoid this bug. Well of course, use Apache or Linux
also "fix" this problem as well.
BTW, FastCGI is an excellent idea to make PHP more stable. But I am
worry it becomes a way to hide all the thread-safe, memory leak issues
and allow them not being fixed properly.
[2009-02-06 08:57:32] paj...@php.net
As I can't reproduce it this bug, I wonder why you insist to use the
ISAPI? There is now a fastcgi interface for II5/6/7 and it works _way_
better than the ISAPI.
Does the crash happen too when you use a simple script (say phpinfo())
and using the same procedure?
[2009-02-05 07:24:04] sikle at stx dot net
yep, this is definitely a vista/php/isapi problem. It happens so
frequently that I think a fix would really help!
[2009-02-03 21:19:57] tser at deltacontrols dot com
I have updated the bug with backtrace and have contacted the assigned
developer directly (and convinced him that there is no extension
involved in the crash).
However, since I am not the originator, I cannot change the Status.
Please change the status.
Thanks!
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/38111
--
Edit this bug report at http://bugs.php.net/?id=38111&edit=1
