Description of problem:
Issue is described in detail at https://bugs.php.net/bug.php?id=50027
A comment from the PHP bug tracker describes in full:
We encountered this bug yesterday (we could reproduce it quite easily with our code, but unfortunately we cannot disclose it), debugged it, found out that it was due to the GC corrupting the std_object_handlers prototype and once we knew that, we checked with the svn repo and saw that that was fixed in r303016.
The corruption that happens is that the read_property field of std_object_handlers gets set to NULL, because the GC treated the handler as a zval.
The bug is already fixed upstream in PHP 5.3.4 but as far as I could determine from the release notes within the rpm it is not yet backported by Red Hat to 5.3.3.
Because the bug causes complete application failure it should be considered as potentially serious enough to warrant backport, or otherwise considered for inclusion in the next release.
Version-Release number of selected component (if applicable):
I think this is the same issue than Bug #848186.
For now, I really cannot reproduce this issue, have you any simple reproducer script ?
> I think this is the same issue than Bug #848186.
Apologies for the duplicate if that's the case. Unfortunately that bug doesn't seem to be publicly accessible so I couldn't find it when searching.
> For now, I really cannot reproduce this issue, have you any simple reproducer script ?
There is not a simple test case I can share (yet). We are still working on this and I will try to provide if possible.
In the meantime we have verified that running 5.3.17 does not exhibit the errors - so there is definitely a bug fixed between php-5.3.3-14.el6_3.x86_64 and 5.3.17 (PHP Group stock version) responsible for the behaviour we found.
Our analysis points to the mentioned 50027 PHP Group bug report (fix for this was applied in 5.3.4) but we are still working to confirm which exact 5.3.x release introduces the fix for the problem we observed to make absolutely certain that 50027 is the bug responsible for it.
Regardless though, the bug in 50027 exists and was fixed by PHP Group - do you consider the issue itself to be important enough to backport, because it causes application code to crash (PHP Group already identified and confirmed this to be the case).
Research suggests it to commonly occur when writing an application built on top of the Zend Framework (there is probably some sequence of functions it uses which trigger it), so that is probably the best starting point for trying to build a test case to reproduce the bug. If we manage to produce a simple reproducer script I will be happy to share it.
An experimental test package is available here:
which has the upstream patch for the Zend garbage collector applied.
Since we've been unable to reproduce this issue internally (thus far), we'd very much appreciate hearing the results of any testing with these packages.
Please leave a comment here when you have downloaded the packages from that location.
Tested with the package provided and the errors experienced previously (when using the standard 5.3.3-14) are confirmed fixed.
We believe we've identified this issue in some of our production servers...
I'm not seeing any reference that this has actually been release for RHEL, has it been released or is there a way to receive the patched RPM? It appears that link above is no longer functional for recieving the patch...
(In reply to comment #4)
> An experimental test package is available here:
which has the upstream patch for
> the Zend garbage collector applied.
Since we've been unable to reproduce
> this issue internally (thus far), we'd very much appreciate hearing the
> results of any testing with these packages.
Please leave a comment here
> when you have downloaded the packages from that location.
Jonathan - if you contact Red Hat Support they should be able to get you the appropriate RPMs; explain this is a known issue and reference this bug number. E-mail me if you need further assistance.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.