Edit report at https://bugs.php.net/bug.php?id=51159&edit=1
ID: 51159
Updated by: ar...@php.net
Reported by: achristianson at yakabod dot com
Summary: session_set_save_handler Memory Corruption
-Status: Open
+Status: Feedback
Type: Bug
Package: Scripting Engine problem
Operating System: CentOS 5.4
PHP Version: 5.3.1
Block user comment: N
Private report: N
New Comment:
The reproduce code correctly gives a fatal error ("Fatal error: Cannot access
self:: when no class scope is active" and no crash) in the current 5.3 branch
and trunk. Changing it to a normal variable assignment works fine.
Please let us know if you can reproduce this bug with another script without
this error, or a current PHP version.
Previous Comments:
------------------------------------------------------------------------
[2011-01-27 22:23:21] sa at yakabod dot com
Any chance someone can take a look at this issue that is now approaching 1 year
in the queue. We have recently reproduced it on PHP 5.3.4 on CentOS 5.5. We
are
willing to help out with debugging. Thanks.
------------------------------------------------------------------------
[2010-05-26 19:37:14] info at das-peter dot ch
Hi there,
can confirm this behavior with gc enabled/disabled.
My current installation:
php 5.3.2 for win x86 [API220090626,TS,VC6 ]
Compiler VC6, thread safe
Run under Apache 2.2
Cheers,
Peter
------------------------------------------------------------------------
[2010-03-01 12:46:00] achristianson at yakabod dot com
We tried with GC off and we get the same result.
------------------------------------------------------------------------
[2010-02-28 16:52:02] j...@php.net
Try turn garbage collection of so we know if it's that.. zend.enable_gc = off,
IIRC. :)
------------------------------------------------------------------------
[2010-02-26 19:08:01] achristianson at yakabod dot com
We tried this with Zend MM and garbage collection turned on and off. No
change in result.
------------------------------------------------------------------------
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=51159
--
Edit this bug report at https://bugs.php.net/bug.php?id=51159&edit=1
