Edit report at https://bugs.php.net/bug.php?id=73183&edit=1
ID: 73183
User updated by: schnederle at futureweb dot at
Reported by: schnederle at futureweb dot at
Summary: Segfaults / zend_mm_heap corrupted
Status: Open
Type: Bug
Package: Reproducible crash
Operating System: Centos 7.2.1511
PHP Version: 7.0.11
Block user comment: N
Private report: N
New Comment:
another segfault - BT:
http://temp.in.futureweb.at/php/core.23374.bt.txthttp://temp.in.futureweb.at/php/core.25625.bt.txt
Previous Comments:
------------------------------------------------------------------------
[2016-09-29 08:46:34] schnederle at futureweb dot at
Please find BT here: http://temp.in.futureweb.at/php/core.30883.bt.txt
------------------------------------------------------------------------
[2016-09-28 15:31:46] laruence@php.net
paste the backtrace out (coredump)
------------------------------------------------------------------------
[2016-09-28 11:25:50] schnederle at futureweb dot at
again Segfaults with opcache.protect_memory=1:
[Wed Sep 28 13:22:25.387677 2016] [core:notice] [pid 25800] AH00052: child pid 4680 exit signal
Segmentation fault (11)
...
[Wed Sep 28 13:22:46.415573 2016] [core:notice] [pid 25800] AH00052: child pid 4885 exit signal
Segmentation fault (11)
------------------------------------------------------------------------
[2016-09-28 08:01:54] schnederle at futureweb dot at
alright - I activated protect_memory and will report back.
Will I see Errors in the Logs when there are any unexpected writes to shared memory? (unfortunately
there is not much documentation available what protect_memory excactly does)
------------------------------------------------------------------------
[2016-09-28 03:39:24] laruence@php.net
you may try to set opcache.protect_memory=1 (please note this will significantly slowdown the
server). and see if there is any unexpected write to shared memory
------------------------------------------------------------------------
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=73183
--
Edit this bug report at https://bugs.php.net/bug.php?id=73183&edit=1