Hi, On Fri, October 3, 2014 12:09, Leon Stringer wrote: > On 1 October 2014 17:02, Leon Stringer <leon.stringer@xxxxxxxxxxxx> > wrote: > > >> On 1 October 2014 16:44, Anatol Belski <anatol.php@xxxxxxxxxx> wrote: >> >> >>> Hi, >>> >>> >>> On Wed, October 1, 2014 14:18, Leon Stringer wrote: >>> >>>> Hi, >>>> >>>> >>>> >>>> I'm running Moodle on a Microsoft Windows Server 2008 R2 64-bit >>>> server with Apache and PHP (both 32-bit). >>>> >>>> >>>> I was getting Apache crash regularly (e.g. 10 times an hour) with >>>> the following error being logged: >>>> >>>> Faulting application name: httpd.exe, version: 2.2.17.0, time >>>> stamp: >>>> 0x4cbbe9e8 >>>> Faulting module name: php5ts.dll, version: 5.3.5.0, time stamp: >>>> >>> 0x4d26013e >>> >>>> Exception code: 0xc0000005 >>>> Fault offset: 0x0000c699 >>>> Faulting process id: 0x335c >>>> Faulting application path: C:\Moodle25\server\apache\bin\httpd.exe >>>> Faulting module path: C:\Moodle25\server\php\php5ts.dll >>>> >>>> >>>> >>>> OK, these versions are pretty old so I upgraded but I'm still >>>> getting (presumably) the same error: >>>> >>>> >>>> >>>> Faulting application name: httpd.exe, version: 2.4.10.0, time >>>> stamp: >>>> 0x53c79afa >>>> Faulting module name: php5ts.dll, version: 5.5.17.0, time stamp: >>>> 0x5418c5a5 >>>> Exception code: 0xc0000005 >>>> Fault offset: 0x0004b985 >>>> Faulting process id: 0xf34 >>>> Faulting application path: E:\Server\Apache24\bin\httpd.exe >>>> Faulting module path: E:\Server\PHP\php5ts.dll >>>> >>>> >>>> >>>> Does anyone have any advice on troubleshooting this? E.g. for >>>> getting enough information to log a bug? >>>> >>>> Moodle is pretty stable, but even if it had a problem I wouldn't >>>> expect >>> a >>>> crash. >>>> >>>> Thanks in advance, >>>> >>>> >>>> >>>> Leon >>>> >>>> >>> what I would like to know yet is - where your PHP and Apache builds >>> descend from. >>> >>> And for the start, please take a look at >>> https://bugs.php.net/bugs-generating-backtrace-win32.php . We need a >>> backtrace to be able to diagnose the issue. Once you have it, please >>> report a bug to bugs.php.net. Ideally were to have some reproduce >>> snippet in PHP as well. >>> >>> Thanks >>> >>> >>> Anatol >>> >>> >>> Thanks for your reply. I can answer the first question straight away: >>> >> they came from >> http://www.apachelounge.com/download/VC11/binaries/httpd-2.4.10-win32-V >> C11.zip >> and >> http://windows.php.net/downloads/releases/php-5.5.17-Win32-VC11-x86.zip >> . >> >> >> Thanks for the link, I'll see if I can capture a backtrace of the >> crash. >> >> > Hi, > > > I've tried to get a backtrace. It's a live server so there are a lot of > Apache threads but hopefully this is the information that's required(?). > > > In the summary is the following message: > > > In > httpd__PID__1840__Date__10_03_2014__Time_09_54_39AM__360__Second_Chance_Ex > ception_C0000005.dmp the assembly instruction at php5ts!zend_execute+c5 in > E:\Server\PHP\php5ts.dll from The PHP Group has caused an access > violation exception (0xC0000005) when trying to write to memory location > 0x00000001 > on thread 60 > > For thread 60 the following is listed: > > > Entry point libhttpd!ap_regkey_value_set+1bf0 > Create time 03/10/2014 09:54:21 > Time spent in user mode 0 Days 00:00:00.811 > Time spent in kernel mode 0 Days 00:00:00.296 > > > This thread is not fully resolved and may or may not be a problem. > Further > analysis of these threads may be required. > > Function Source > > > php5ts!zend_execute+c5 > [c:\php-sdk\php55\vc11\x86\php-5.5.17-ts\zend\zend_vm_execute.h @ 388 + > a4] c:\php-sdk\php55\vc11\x86\php-5.5.17-ts\zend\zend_vm_execute.h @ 388 > + a4 > php5ts!zend_execute_scripts+14a > [c:\php-sdk\php55\vc11\x86\php-5.5.17-ts\zend\zend.c @ 1331] > c:\php-sdk\php55\vc11\x86\php-5.5.17-ts\zend\zend.c @ 1331 > php5apache2_4!php_handler+2e7f > [c:\php-sdk\php55\vc11\x86\php-5.5.17-ts\sapi\apache2handler\sapi_apache2 > .c > @ 669 + e] > c:\php-sdk\php55\vc11\x86\php-5.5.17-ts\sapi\apache2handler\sapi_apache2.c > @ 669 + e > msvcr110!_tolower_l+13 libapr_1!apr_pstrcat+86 msvcr110!__crtFlsGetValue+15 > msvcr110!_getptd_noexit+6a 0x06dd71c0 > php5apache2_4!php_handler+1c1 > [c:\php-sdk\php55\vc11\x86\php-5.5.17-ts\sapi\apache2handler\sapi_apache2 > .c > @ 611 + 3a] > c:\php-sdk\php55\vc11\x86\php-5.5.17-ts\sapi\apache2handler\sapi_apache2.c > @ 611 + 3a > kernel32!BaseThreadInitThunk+e ntdll!__RtlUserThreadStart+70 > ntdll!_RtlUserThreadStart+1b > > Is this the right information? If so, what next? > > > Thanks in advance, > > > Leon > > The builds you're using are fine together, just wanted to ensure that. At the first glance, the BT doesn't reveal any place with an obvious bug. But there is also a mention that "the thread was not fully resolved". Is this BT what you get consistently? Please create a ticket for this. If it's reproduceable on some dev system of yours, maybe you could try again with less threads. And please check if it's possible you to share the dump. Thanks Anatol -- PHP Windows Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
