ID:               37483
 User updated by:  jneill at gamedaytv dot com
 Reported By:      jneill at gamedaytv dot com
-Status:           Feedback
+Status:           Open
 Bug Type:         IIS related
 Operating System: Windows 2003 SP 1
 PHP Version:      5.1.4
 New Comment:

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.


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

[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.

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

[2006-05-24 22:12:35] [EMAIL PROTECTED]

Please try using this CVS snapshot:

  http://snaps.php.net/php5.2-latest.tar.gz
 
For Windows:
 
  http://snaps.php.net/win32/php5.2-win32-latest.zip



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

[2006-05-19 16:04:44] julien dot jacques at fingerprint dot fr

I have exactly the same problem.

Since i am on a production server, i can't install MSVC6. (it seems to
be replace with MSvisual express2005, which require to remove all sql
server prior to 2005. And i can't remove it on production.)
I try to add the .pdb to the DebugDiag symbol path but the file doesn't
match the dll. 

Is this because the debug pack is for php5.2.x?
Do i have to install php5.2.x-dev?
Where can i find the debug pack for php5.1.4?

I would be happy to help, but i don't know how to produce the backtrace
you require.

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

[2006-05-18 17:40:13] jneill at gamedaytv dot com

I do not understand these instructions:

"When PHP crashes, click Cancel to debug the process. Now MSVC starts
up in Debug View. If you don't already see the call stack, go into the
View menu and choose Debug Windows &#8594; Call Stack."

When PHP crashes, we do not see a dialogue box with Cancel as an
option, and MSVC does not start up. All that happens is that we get an
error in the System Event Log that says something like:

---
A process serving application pool 'Site12' terminated unexpectedly.
The process id was '3392'. The process exit code was '0xc0000005'.
---

So how do I run the debugger?

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

[2006-05-17 20:27:21] [EMAIL PROTECTED]

Thank you for this bug report. To properly diagnose the problem, we
need a backtrace to see what is happening behind the scenes. To
find out how to generate a backtrace, please read
http://bugs.php.net/bugs-generating-backtrace.php for *NIX and
http://bugs.php.net/bugs-generating-backtrace-win32.php for Win32

Once you have generated a backtrace, please submit it to this bug
report and change the status back to "Open". Thank you for helping
us make PHP better.



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

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

Reply via email to