Edit report at https://bugs.php.net/bug.php?id=66460&edit=1
ID: 66460
User updated by: spam2 at rhsoft dot net
Reported by: spam2 at rhsoft dot net
Summary: PHP 5.5.7 and 5.5.8 horrible unstable
Status: Closed
Type: Bug
Package: opcache
Operating System: Linux
PHP Version: 5.5.8
Assigned To: rasmus
Block user comment: N
Private report: N
New Comment:
> Sounds like a different bug
pretty sure because on https://bugs.php.net/bug.php?id=66474 you said
solved by https://github.com/zendtech/ZendOptimizerPlus/archive/master.zip
and that is why any change after 5.5.6 in ext/opcache should be reverted
because not a single bug there could have the same bad impact as the "fixes"
Previous Comments:
------------------------------------------------------------------------
[2014-01-16 02:25:28] phpdev at ehrhardt dot nl
Sounds like a different bug. The only way to make sure is, really, trying the block_pass.c from the
5.5.6 tarball and the other files from the 5.5.8 tarball.
------------------------------------------------------------------------
[2014-01-16 02:17:10] spam2 at rhsoft dot net
> Did you ever try the block_pass.c from the 5.5.6 tarball
> and the other files from the 5.5.8 tarball?
no, only 5.5.6 opcache on 5.5.8 source and head opcache on 5.5.8 source
both have the same segfault-behavior obviously introduced in 5.5.7
i noticed this a few times before christmas on local machines but
not predictable to reproduce and calling the same page 100000 times
with a benchmark after restart httpd may not trigegr a single segfault
due a lot of updates in system libraries in the first front i was unsure
if there was something broken, starting with 2014/01/07 i upgraded servers
from Fedora 18/PHP 5.4 to Fedora 19 PHP/5.5, tests looked fine and after
teh first low-trafficserver the segfaults in the apache-errorlog started
heavily, so i downgraded to PHP 5.5.6 quickly
the day before i found something with such sgefaults in context of
"zend.enable_gc", disabled it and for a short time it looked OK
finally after 5.5.8 had the same issues and no predictable way to
reproduce i started playing around with configuration, one of the
first things was to disable opcache, not a single segfault
since downgrade to 5.4 would have been way too much work i tried
the 5.5.6 opcache because i had PHP 5.5 over months on my development
machines and faced the problem not until december
so the only thing i currently can say is that in case of the Linux
kernel *any* commit to opcache after 5.5.6 would have been *reverted*
completly
> because many people run with the optimization_level set to 0
i doubt that because it's not default
------------------------------------------------------------------------
[2014-01-16 02:05:03] phpdev at ehrhardt dot nl
Did you ever try the block_pass.c from the 5.5.6 tarball and the other files from the 5.5.8 tarball?
------------------------------------------------------------------------
[2014-01-16 01:33:00] spam2 at rhsoft dot net
> Look at the dates please. This was fixed after 5.5.8 was released
> which is why I asked you to try the current code, not the 5.5.8
> release.
i took the source of https://github.com/zendtech/ZendOptimizerPlus/archive/master.zip
and replaced the "opcache" folder of 5.5.8 tarball the same way as i described above i did
with the "opcache" folder from 5.5.6 to replace the broken 5.5.8 "ext/opcache"
> And it wasn't noticed because many people run with the
> optimization_level set to 0
i did not change the optimization_level setting anywhere
> and it is also a weird edge-case script that triggers the bug
PHP after 5.5.6 as well as https://github.com/zendtech/ZendOptimizerPlus/archive/master.zip
triggers segfaults not only with edge-case scripts, it triggers them with any code we run the last
10 years, the only interesting is that apache benchmarks do not trigger it - but why do i need
explain that all again?
------------------------------------------------------------------------
[2014-01-16 01:05:11] rasmus@php.net
Look at the dates please. This was fixed after 5.5.8 was released which is why I asked you to try
the current code, not the 5.5.8 release. And it wasn't noticed because many people run with the
optimization_level set to 0 and it is also a weird edge-case script that triggers the bug.
------------------------------------------------------------------------
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=66460
--
Edit this bug report at https://bugs.php.net/bug.php?id=66460&edit=1