Edit report at https://bugs.php.net/bug.php?id=60457&edit=1
ID: 60457 Updated by: maar...@php.net Reported by: Sjon at hortensius dot net Summary: gc_zval_possible_root SIGSEGV -Status: Open +Status: Closed Type: Bug Package: Scripting Engine problem Operating System: Linux PHP Version: 5.3.8 -Assigned To: +Assigned To: maarten Block user comment: N Private report: N New Comment: Fixed in related issue :) Previous Comments: ------------------------------------------------------------------------ [2012-01-27 13:19:23] no at snaxor dot com It appears that the bug #60701 referenced by Sjon at hortensius dot net was the responsible for the crashes in my application. ------------------------------------------------------------------------ [2012-01-20 13:37:39] sjon at hortensius dot net This bug has been solved in a more specific bug which includes a patch: https://bugs.php.net/bug.php?id=60701 ------------------------------------------------------------------------ [2012-01-04 08:26:51] Sjon at hortensius dot net For anyone interested, this bug is not related to a single class, but we have worked around, and seen this bug occur again, in many different places. I have also been reproducing this in 5.3.6 / 5.3.5 / 5.3.4 and 5.3.3 ------------------------------------------------------------------------ [2012-01-04 07:31:07] no at snaxor dot com I may be bumping into this one as well, Similarly, I cannot provide a script to reproduce it since it happens in a project with many classes, but I'll see if I can narrow it down and create one. It is very inconsistent. It will die one the same page but with different data it will be fine. What seems to be sparking it in my case is Smarty, with lots of sub-template files. The content is rendered correctly, but during Smarty's cleanup is when it dies. It is trigger-able via php command line or apache module. gc_disable() doesn't unfortunately have any effect. PHP Version: 5.3.8 on OSX. Program received signal EXC_BAD_ACCESS, Could not access memory. Reason: KERN_INVALID_ADDRESS at address: 0x0000003dca9fd2f1 0x0000000100359618 in gc_zval_possible_root () (gdb) bt #0 0x0000000100359618 in gc_zval_possible_root () #1 0x000000010034a765 in zend_hash_destroy () #2 0x000000010035c86c in zend_object_std_dtor () #3 0x000000010035c4f8 in zend_objects_free_object_storage () #4 0x000000010035faae in zend_objects_store_del_ref_by_handle_ex () #5 0x000000010035fb64 in zend_objects_store_del_ref () #6 0x0000000100334e2d in _zval_ptr_dtor () #7 0x000000010034a765 in zend_hash_destroy () #8 0x000000010033f1b0 in _zval_dtor_func () #9 0x0000000100334e2d in _zval_ptr_dtor () #10 0x000000010034a765 in zend_hash_destroy () #11 0x000000010035c86c in zend_object_std_dtor () #12 0x000000010035c4f8 in zend_objects_free_object_storage () #13 0x000000010035f6eb in zend_objects_store_free_object_storage () #14 0x0000000100337750 in shutdown_executor () #15 0x000000010033feae in zend_deactivate () #16 0x00000001002f08b1 in php_request_shutdown () #17 0x00000001003ba366 in main () #18 0x00000001000010ec in start () ------------------------------------------------------------------------ [2011-12-12 15:58:33] Sjon at hortensius dot net I am afraid not, gc_disable() doesn't solve this segfault unfortunately ------------------------------------------------------------------------ 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=60457 -- Edit this bug report at https://bugs.php.net/bug.php?id=60457&edit=1
