Edit report at https://bugs.php.net/bug.php?id=69233&edit=1
ID: 69233
Comment by: quantuumsnot at gmail dot com
Reported by: julientld at free dot fr
Summary: PHP-CGI.EXE and OPCache crash with error code
0xc0000005
Status: Open
Type: Bug
Package: opcache
Operating System: Windows Server 2012
PHP Version: 5.6.7RC1
Block user comment: N
Private report: N
New Comment:
To add some clarity - php is the thread-safe version
Previous Comments:
------------------------------------------------------------------------
[2015-05-13 16:55:59] quantuumsnot at gmail dot com
Same issue under Windows 7 x64 and php-5.6.8-Win32-VC11-x64
Disabling the whole extension dll solves it.
opcache.enable_cli=0 doesn't help
------------------------------------------------------------------------
[2015-03-24 17:01:50] julientld at free dot fr
Yes, I have seen your bug report #69067. I hope someone from the dev team will give us soon infos
about that.
------------------------------------------------------------------------
[2015-03-24 16:51:27] deivid dot garcia dot garcia at gmail dot com
I reported something similar in another PHP issue:
https://bugs.php.net/bug.php?id=69067
Opcode cache is failing intermitently on windows systems.
There is a chance that these issues are not related to a specific script but to zend engine not
properly managing things under tough conditions (at least in windows) such as forecefully shtudown
processes or high memory pressure.
------------------------------------------------------------------------
[2015-03-22 09:36:52] julientld at free dot fr
Hello,
Before suspending this bug, perhaps someone could answer my last comment ? The bug is absolutely not
solved. Strange practice to investigate a bug.
Has anybody from the OPCache team studied the supplied backtrace ? I don't see what additional
feedback I can give you as explained.
Thanks.
------------------------------------------------------------------------
[2015-03-22 04:22:19] php-bugs at lists dot php dot net
No feedback was provided. The bug is being suspended because
we assume that you are no longer experiencing the problem.
If this is not the case and you are able to provide the
information that was requested earlier, please do so and
change the status of the bug back to "Re-Opened". Thank you.
------------------------------------------------------------------------
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=69233
--
Edit this bug report at https://bugs.php.net/bug.php?id=69233&edit=1