ID: 44047
User updated by: matthew dot horner at redprairie dot com
Reported By: matthew dot horner at redprairie dot com
Status: Bogus
Bug Type: IIS related
Operating System: Windows Vista
PHP Version: 5.2.5
New Comment:
Am I missing something here? I posted code to reproduce the crash as
well as back trace. I initially open the report with that information.
At which time, you and one other developer suggested taking the latest
snapshot and removing all extensions. Didn't appear to be bogus at that
time.
Was moving the report to a reproducible crash the reason you decided to
call this a bogus issue? I can reproduce a crash with the most basic
PHP script. As nonya and I have found, this issue is not specific to
IIS but the IIS and PHP 5.1/5.2 code branches.
I opened this report 2 months ago and haven't seen any progress. If
you are addressing this issue on another report, then can you please
provide the bug #? I understand that I am reporting this issue with
Windows Vista/IIS 7. Windows Server 2008 has been released and
deploying IIS 7. I can only figure this is going to become a much
larger issue in the coming months.
FastCGI is an option, but is not the only option. Apache is also an
option, but I can't force all implementations to require Apache.
Previous Comments:
------------------------------------------------------------------------
[2008-04-08 11:02:21] [EMAIL PROTECTED]
We are aware of PHP's problems with stability under IIS and are working
to rectify the problem. Unfortunatly your bug report does not contain
any
extra useful information and we already have enough bug reports open
about
this issue. If you can provide more detailed information such as a
reproducable crash or a backtrace please do so and reopen this bug.
Otherwise please keep trying new releases as we are working to resolve
the problems on this platform
Thanks for your interest in PHP.
It's safest to use FastCGI. Even IIS supports it nowadays..
------------------------------------------------------------------------
[2008-04-07 18:21:51] matthew dot horner at redprairie dot com
Thank you for your observation. I am not sure if I had originally set
it this way or not, but I have changed the category to hopefully
represent the issue better. Maybe this will get noticed by someone who
will engage the issue and provide a fix.
------------------------------------------------------------------------
[2008-04-03 20:20:58] nonya at spam dot this
I see this topic has been labeled an IIS issue and there was no
response from PHP staff.
If it is a IIS7 issue, why was it not occurring in PHP4?
------------------------------------------------------------------------
[2008-03-19 04:22:41] jaedsm at hotmail dot com
Having the same issue here too. Installed IIS7 and PHP 5.2.5 the other
day on my home system running Vista Home Premium. Didn't consider it
would have been caused by some timeout but after reading here that makes
sense.
No crash message has appeared while I've been working for hours on end,
once I stop though it appears a little while later and doesn't appear
again unless I load another php page.
------------------------------------------------------------------------
[2008-03-06 14:00:56] matthew dot horner at redprairie dot com
I would still consider this a workaround, as this is not standard
procedure for installing ISAPI modules in IIS7. Furthermore, this issue
is not an issue with PHP 4. Which to me, would indicate there is
something coded differently with PHP 5 to cause the crash when recycling
the process. Also, reconfiguring the Application Pool, affects more
than just your pool hosting PHP driven applications. What side effects
there are, is unclear to me, but certainly not something I would like to
find out about once a site is in production.
I posted this bug because I would like to have the PHP developers debug
this issue and determine if there is indeed a code problem or a problem
with IIS7. Not to have a workaround to avoid crashes on IIS7.
I am not disputing the fact that your solution works. However, this
appears to be an issue and should be addressed at the PHP level first.
Thank you for your suggestions.
------------------------------------------------------------------------
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/44047
--
Edit this bug report at http://bugs.php.net/?id=44047&edit=1
