ID: 37483
Comment by: gravityworksllc at hotmail dot com
Reported By: jneill at gamedaytv dot com
Status: Open
Bug Type: IIS related
Operating System: Windows 2003 SP 1
PHP Version: 5.1.4
New Comment:
I just installed mysql.5.0.22 and the w3wp errors stopped even though I
am using php 5.1.4. Very strange... But it works and it works well.
Also using MYSql Admin 1.1 ( latest revision ) Installed php 5.1.4
then MYSql 5.0.22 and then SQLAdmin 1.1. No more errors from w3wp.exe
and anything.. Clean as a whistle...
Kind regards,
Mynd
Previous Comments:
------------------------------------------------------------------------
[2006-06-12 20:07:18] mike at normi dot net
Can confirm this on Windows 2003 SP1, ISAPI extension is as unstable as
hell since 5.1.4.
------------------------------------------------------------------------
[2006-06-10 11:31:13] hayden dot kirk at mobilepc dot co dot nz
I have the same error on Windows 2003 SP1 and Windows 2003 SBS SP1.
------------------------------------------------------------------------
[2006-05-30 17:59:06] bruno dot delbono at gmail dot com
I too can replicate it on both the 5.2-devel (the current) and 5.1.4.
This is becoming a very irritating problems as w3wp.exe keeps crashing.
Windows 2003 SP1 running IIS 6 with PHP ISAPI.
Faulting application w3wp.exe, version 6.0.3790.1830, faulting module
unknown, version 0.0.0.0, fault address 0x01b05c80.
WARNING - DebugDiag was not able to locate debug symbols for
php5ts.dll, so the information below may be incomplete.
In
w3wp__PID__4176__Date__05_25_2006__Time_09_57_31AM__495__Second_Chance_Exception_C0000005.dmp
an access violation exception (0xC0000005) occured on thread 18 when
another module attempted to call the following unloaded module:
php5ts.dll.
w3wp__PID__4176__Date__05_25_2006__Time_09_57_31AM__495__Second_Chance_Exception_C0000005.dmp
Type of Analysis Performed Crash Analysis
Machine Name DRAGOS
Operating System Windows Server 2003 Service Pack 1
Number Of Processors 2
Process ID 4176
Process Image c:\WINDOWS\system32\inetsrv\w3wp.exe
System Up-Time 1 day(s) 06:47:17
Process Up-Time 0 day(s) 01:19:11
Thread 18 - System ID 2008
Entry point msvcrt!_endthread+3b
Create time 5/25/2006 9:57:30 AM
Time spent in user mode 0 Days 0:0:0.0
Time spent in kernel mode 0 Days 0:0:0.0
Function Arg 1 Arg 2 Arg 3 Source
<Unloaded_php5ts.dll>+265c80 02e8a940 00000000 00000000
msvcrt!_endthread+ab 02db8bf8 00000000 00000000
kernel32!BaseThreadStart+34 77bcb35a 02db8bf8 00000000
In
w3wp__PID__4176__Date__05_25_2006__Time_09_57_31AM__495__Second_Chance_Exception_C0000005.dmp
an access violation exception (0xC0000005) occured on thread 18 when
another module attempted to call the following unloaded module:
php5ts.dll.
------------------------------------------------------------------------
[2006-05-30 16:37:24] jneill at gamedaytv dot com
We tested the 5.2 snap on two of our Windows 2003 SP1 servers, and the
aforementioned crashes occur with more frequency than with PHP 5.1.4 on
the same servers.
------------------------------------------------------------------------
[2006-05-29 09:22:29] andrej at seznam dot org
I came up with exact the same crash analysis, even with the latest PHP
snapshot 5.2.0-dev dated May 28 2006 00:17:10:
---
Operating System Windows Server 2003 Service Pack 1
Number Of Processors 2
Process ID 8060
Process Image c:\WINDOWS\system32\inetsrv\w3wp.exe
System Up-Time 46 day(s) 02:14:04
Process Up-Time 0 day(s) 00:22:07
Thread 15 - System ID 7536
Entry point msvcrt!_endthread+3b
Create time 29.5.2006 0:13:40
Time spent in user mode 0 Days 0:0:0.0
Time spent in kernel mode 0 Days 0:0:0.0
Function Arg 1 Arg 2 Arg 3 Source
<Unloaded_php5ts.dll>+268810 01626ce0 00000000 00000000
msvcrt!_endthread+ab 0270aa78 00000000 00000000
kernel32!BaseThreadStart+34 77bcb35a 0270aa78 00000000
an access violation exception (0xC0000005) occured on thread 15 when
another module attempted to call the following UNLOADED module:
php5ts.dll.
---
It is weird, that at the moment of crash sometimes there is NO ACTIVITY
(= noone is browsing the page).
On the other hand, w3swc.exe process consumes too much CPU time,
compared to my observations from some time ago, when WebAppPools did
not crash.
The observed WebAppPool is isolated, I mean, only 1 web uses this pool.
------------------------------------------------------------------------
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/37483
--
Edit this bug report at http://bugs.php.net/?id=37483&edit=1