php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Bug #37366 IIS 6.0 w3wp process crash with PHP 5.1.4
Submitted: 2006-05-08 14:07 UTC Modified: 2006-05-10 10:15 UTC
Votes:4
Avg. Score:5.0 ± 0.0
Reproduced:4 of 4 (100.0%)
Same Version:4 (100.0%)
Same OS:4 (100.0%)
From: chris dot schreiber at fast4gl dot com Assigned:
Status: Not a bug Package: Reproducible crash
PHP Version: 5.1.4 OS: Windows 2003 Server
Private report: No CVE-ID: None
 [2006-05-08 14:07 UTC] chris dot schreiber at fast4gl dot com
Description:
------------
This problem occurs using the newest builds of PHP, both 5.1.3 and 5.1.4.  This did not happen with 5.1.2 or earlier versions.

Running IIS 6.0 on Windows 2003 Server Enterprise.  Running PHP in ISAPI mode.

w3wp.exe processes crash throughout the day, about 20-30 times.  Several process instances will usually crash together at the same time, and then be ok for a couple of hours until happening again.

Error is:
w3wp.exe - Application Error : The instruction at "0x01b55c80" referenced memory at "0x01b55c80". The memory could not be "read".

The memory address is always either "0x01b55c80" or "0x01b55c90".

Here is a link to my PHPinfo():
http://mail.fast4gl.net/phpinfo.php

Reproduce code:
---------------
Running vBulletin (3.5.4).  Can't track down any code which produces the crash.


Patches

Add a Patch

Pull Requests

Add a Pull Request

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2006-05-08 15:48 UTC] gravityworksllc at hotmail dot com
I can validate this error.  I get this along with the pool process crashing.  This was fine in version 5.12.  If you need more information on the errors please let me know.

Kind regards,
Mynd

www.myndpollution.com
 [2006-05-08 21:25 UTC] paul at routingcore dot com
I get the same thing. I hadn't updated since 5.0.4, which works fine for me. As soon as I drop 5.1.4 in I get the application errors for w3wp.exe. I set IIS to recycle the worker threads every couple of minutes to see if the frequency of the errors would increase, and they did.
 [2006-05-09 16:45 UTC] zbowden at vt dot edu
I'm seeing w3sp.exe processes crash but I'm not seeing the same Application Errors. The evidence I see are event id 1009's in my System Event logs saying the application pool terminated unexpectedly. Are you all seeing the application errors in the event logs or as pop ups? By chance are you seeing anything getting recorded in your event logs that correspond to this as well?
 [2006-05-09 17:08 UTC] chris dot schreiber at fast4gl dot com
I'm getting the errors as an application popup message.  These are also automatically logged into the System Event Viewer log as Event ID 26.
 [2006-05-09 18:06 UTC] gravityworksllc at hotmail dot com
It is a combination of all 3, you will get the popups if you reboot the server, you will get the pool crash in your event log as well as the w3wp's.  

I have about 50 today already.. I hope they get this sorted and fast.

Kind regards, 
Mynd

www.myndpollution.com
 [2006-05-09 18:35 UTC] zbowden at vt dot edu
Thanks for the feedback guys, it does sound like I'm seeing the same things you all are. Not that this is uplifting/encouraging since it's been open since March, but I think this bug may be what we're seeing too:
http://bugs.php.net/bug.php?id=36853

Maybe this will help with getting this one assigned and fixed (perhaps to tony2001@php.net?).
 [2006-05-10 10:15 UTC] tony2001@php.net
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.


 
PHP Copyright © 2001-2024 The PHP Group
All rights reserved.
Last updated: Thu Apr 18 08:02:42 2024 UTC