Bug #66460 [Com]: PHP 5.5.7 and 5.5.8 horrible unstable

From: Date: Thu, 16 Jan 2014 02:05:04 +0000
Subject: Bug #66460 [Com]: PHP 5.5.7 and 5.5.8 horrible unstable
References: 1  Groups: php.bugs 
Request: Send a blank email to php-bugs+get-183825@lists.php.net to get a copy of this message
Edit report at https://bugs.php.net/bug.php?id=66460&edit=1

 ID:                 66460
 Comment by:         phpdev at ehrhardt dot nl
 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:

Did you ever try the block_pass.c from the 5.5.6 tarball and the other files from the 5.5.8 tarball?


Previous Comments:
------------------------------------------------------------------------
[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.

------------------------------------------------------------------------
[2014-01-15 22:03:25] spam2 at rhsoft dot net

> #66474 made my opcache stable again. Thank you

unconfirmed, see my commetn at that bugreport

i replaced the "opcache" folder from 5.5.8 tarball with the linked
master and from the first request on our asterisk-backend segfaults

how can it be that *two* following stable releases are that broken

------------------------------------------------------------------------
[2014-01-15 21:30:45] spam008 at evil dot net dot pl

#66474 made my opcache stable again. Thank you.

------------------------------------------------------------------------
[2014-01-15 21:14:56] rasmus@php.net

Yes, we know it was the block_pass change as mentioned in previous comments here and https://bugs.php.net/bug.php?id=66474 has a
reproducing PHP code snippet. This issue was fixed, so if you want to help, make sure you are
building current HEAD (triple-check that you are replacing the newly .so correctly and restarting)
because everyone else who had this same issue is reporting it is solved in the current code. If you
can still make it crash with the current code, try to find the code snippet that does it and verify
that it doesn't crash with opcache.optimization_level=0

------------------------------------------------------------------------


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


Thread (32 messages)

« previous php.bugs (#183825) next »