ID:               45786
 Comment by:       karelevzen at gmail dot com
 Reported By:      karelevzen at gmail dot com
 Status:           Assigned
 Bug Type:         CGI related
 Operating System: Windows Vista Ultimate x64 SP1
 PHP Version:      5.3CVS-2008-08-10 (CVS)
 Assigned To:      dmitry
 New Comment:

If this helps, I have created a dump 6 seconds after executing the
page.
Thread 0:
ntdll!NtDelayExecution+15    
kernel32!SleepEx+62    
kernel32!Sleep+f    
php5ts!php_get_inf+1eaf    
php5ts!execute+cc5    
php5ts!execute+6130 

Thread 1:
user32!NtUserGetMessage+15    
user32!GetMessageA+a2    
php5ts!zend_timeout+1a8

Another thing I found interesting is, that upon the request, a
php-cgi.exe is created and does nothing. After the timeout, in the same
exact moment, a new php-cgi.exe is created, the old php-cgi.exe is
destroyed and the page is rendered. Is this behaviour normal or should I
futher investigate this strange process?

This second php-cgi.exe process is destroyed upon refresh and the
display of the IIS error message.


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

[2008-08-18 15:58:20] karelevzen at gmail dot com

No succes, sorry.
It behaves the same, eg. it loads the content, then keeps "loading" for
some time (faulty php module). This time, the GUI error message DOES NOT
APPER, but when I hit refresh, it displays a IIS error message stating:

HTTP Error 500.0 - Internal Server Error
Module  FastCgiModule
Notification    ExecuteRequestHandler
Handler PHP
Error Code      0x8007000d

After another refresh the page again loads, keeps on loading for a
while, than, after another refresh the same error appears.

IMHO it's the same problem, but this time IIS realizes that an error
had occured when the second request is received.

Due to the GUI error not showing, I cannot send you a crushdump.

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

[2008-08-18 11:03:30] [EMAIL PROTECTED]

Could you please retest CVS.

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

[2008-08-13 14:22:26] [EMAIL PROTECTED]

Dmitry, something fishy with request shutdown in fastcgi? Note the ini
options used by the user:

cgi.force_redirect = 0
cgi.fix_pathinfo=1
fastcgi.impersonate = 1


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

[2008-08-13 10:32:13] karelevzen at gmail dot com

So hey, I managed to find a 5.3 release WITH debug files at
http://downloads.php.net/pierre/ ! Here is the complete bugtrace.

php_cgi!fcgi_free_var+4     00000000     001b2638     00c0ddcc    
php5ts!zend_hash_destroy+27     00c0fe00     00000010     00000001    
php_cgi!fcgi_finish_request+2f     00c0ddcc     001b2638     001b2708  
 
php_cgi!fcgi_accept_request+17     00c0ddcc     00000000     00000000  
 
php_cgi!main+69f     00000001     001b2638     001b1690    
php_cgi!mainCRTStartup+e3     7efde000     00c0ffd4     7752cfed    
kernel32!BaseThreadInitThunk+e     7efde000     7770f651     00000000  
 
ntdll!__RtlUserThreadStart+23     00405ed6     7efde000     00000000   

ntdll!_RtlUserThreadStart+1b     00405ed6     7efde000     00000000   





PHP_CGI!FCGI_FREE_VAR+4In
php-cgi__PID__4064__Date__08_13_2008__Time_12_29_14PM__838__Second_Chance_Exception_C0000005.dmp
the assembly instruction at php_cgi!fcgi_free_var+4 in C:\Program Files
(x86)\php\php-cgi.exe from The PHP Group has caused an access violation
exception (0xC0000005) when trying to read from memory location
0x00000000 on thread 0

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

[2008-08-13 06:28:16] karelevzen at gmail dot com

I did that.I've downloaded the debug pack, unpacked it to:
C:\Users\karel_evzen\Desktop\php-dbg and set the Symbol search path for
analysis option in Debug Diagnostic Tool to:
C:\Users\karel_evzen\Desktop\php-dbg
Yet I get the symbols not found warning. Am I missing something?
The debug pack contains runnable PHP, no pdb files. I cant find pdb
files for the current 5.3 snapshot. Try it yourself.

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

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/45786

-- 
Edit this bug report at http://bugs.php.net/?id=45786&edit=1

Reply via email to