Bug #65247 [Com]: php.exe crashes when opcache.enable_cli=1

Edit report at https://bugs.php.net/bug.php?id=65247&edit=1 ID: 65247 Comment by: me at laurinkeithdavis dot com Reported by: me at laurinkeithdavis dot com Summary: php.exe crashes when opcache.enable_cli=1 Status: Feedback Type: Bug Package: Reproducible crash Operating System: Windows 7 x64 PHP Version: 5.5.0 Block user comment: N Private report: N New Comment: Ok, now I think I'm loading the symbols (thought I was before, but maybe not), but I still don't know for sure if I'm doing it right. Though, this one is slightly different: Thread 0 - System ID 740 Entry point php!sapi_cli_single_write+88e6 Create time 7/16/2013 11:39:19 AM Time spent in user mode 0 Days 0:0:0.15 Time spent in kernel mode 0 Days 0:0:0.62 Full Call Stack Function Arg 1 Arg 2 Arg 3 Arg 4 Source ntdll!NtRaiseException+12 00b5f354 00b5f3a4 00000000 00000000 ntdll!RtlReportException+20 00b5f354 00b5f3a4 00000000 00b5f880 ntdll!RtlpTerminateFailureFilter+14 c0000374 00b5f254 774073bc 00000000 ntdll!RtlReportCriticalFailure+67 00000000 00b5f880 773bcfc0 00b5f268 ntdll!_EH4_CallFilterFunc+12 00000000 00000000 00000000 00b5f354 ntdll!_except_handler4+8e fffffffe 00b5f870 00b5f3a4 00b5f328 ntdll!ExecuteHandler2+26 00b5f354 00b5f870 00b5f3a4 00b5f328 ntdll!ExecuteHandler+24 00b5f354 00b5f870 00b5f3a4 00b5f328 ntdll!RtlDispatchException+127 00b5f354 00b5f3a4 00b5f354 00b5f3a4 ntdll!KiUserExceptionDispatcher+f 00b5f354 00b5f3a4 00b5f354 00b5f3a4 Previous Comments: ------------------------------------------------------------------------ [2013-07-16 14:15:09] ab@php.net Ah, me ... php!mainCRTStartup it is ... i'm grieved. Did you load the debug symbols? You might get a better backtrace. As this one is really unusable, that's why it has confused me at the start. ------------------------------------------------------------------------ [2013-07-16 13:19:56] me at laurinkeithdavis dot com Yes, with XDebug disabled, it still crashes. I'm using the php_opcache.dll that is bundled with 5.5 NTS from the windows binaries site. Yes, it still crashes with FastCGI not running (IIS stopped.) If I disable opcache (opcache.enable_cli=0), it does not crash, if I enable (opcache.enable_cli=1), it crashes. How could that not be opcache causing the problem? We've been using wincache for years on the command line and have had no issues. What are we supposed to do? Abandon the use of opcache? ------------------------------------------------------------------------ [2013-07-16 09:03:47] ab@php.net Well, that's a backtrace. Unfortunately it contains nothing about PHP. If that's the BT you only get, that's most likely not opcache. And what about the other questions i've asked - xdebug disabled? Does it crash when fastcgi doesn't run simultaneously on the same machine? Please try just one cli process. ------------------------------------------------------------------------ [2013-07-15 16:10:19] me at laurinkeithdavis dot com Do I do that correctly? ------------------------------------------------------------------------ [2013-07-15 16:09:15] me at laurinkeithdavis dot com Thread 0 - System ID 3728 Entry point php!mainCRTStartup Create time 7/15/2013 11:07:13 AM Time spent in user mode 0 Days 0:0:1.216 Time spent in kernel mode 0 Days 0:0:0.249 Full Call Stack Function Arg 1 Arg 2 Arg 3 Arg 4 Source ntdll!NtRaiseException+12 00abf4b4 00abf504 00000000 00000000 ntdll!RtlReportException+20 00abf4b4 00abf504 00000000 00abf9e0 ntdll!RtlpTerminateFailureFilter+14 c0000374 00abf3b4 776e73bc 00000000 ntdll!RtlReportCriticalFailure+67 00000000 00abf9e0 7769cfc0 00abf3c8 ntdll!_EH4_CallFilterFunc+12 00000000 00000000 00000000 00abf4b4 ntdll!_except_handler4+8e fffffffe 00abf9d0 00abf504 00abf488 ntdll!ExecuteHandler2+26 00abf4b4 00abf9d0 00abf504 00abf488 ntdll!ExecuteHandler+24 00abf4b4 00abf9d0 00abf504 00abf488 ntdll!RtlDispatchException+127 00abf4b4 00abf504 00abf4b4 00abf504 ntdll!KiUserExceptionDispatcher+f 00abf4b4 00abf504 00abf4b4 00abf504 ------------------------------------------------------------------------ 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 https://bugs.php.net/bug.php?id=65247 -- Edit this bug report at https://bugs.php.net/bug.php?id=65247&edit=1