Description of problem: Running phpunit on our testsuite Version-Release number of selected component: php-cli-5.4.11-1.fc18 Additional info: backtrace_rating: 4 cmdline: php /home/christof.damian/workspace/splendia-web/bin/phpunit --configuration /home/christof.damian/workspace/splendia-web/splendia/tests/phpunit-nologging.xml crash_function: gc_zval_possible_root executable: /usr/bin/php kernel: 3.7.2-201.fc18.x86_64 remote_result: NOTFOUND uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 gc_zval_possible_root at /usr/src/debug/php-5.4.11/Zend/zend_gc.c:143 #1 zend_hash_destroy at /usr/src/debug/php-5.4.11/Zend/zend_hash.c:560 #2 _zval_dtor_func at /usr/src/debug/php-5.4.11/Zend/zend_variables.c:45 #3 _zval_dtor at /usr/src/debug/php-5.4.11/Zend/zend_variables.h:35 #4 _zval_ptr_dtor at /usr/src/debug/php-5.4.11/Zend/zend_execute_API.c:438 #6 destroy_zend_class at /usr/src/debug/php-5.4.11/Zend/zend_opcode.c:278 #7 zend_hash_apply_deleter at /usr/src/debug/php-5.4.11/Zend/zend_hash.c:650 #8 zend_hash_reverse_apply at /usr/src/debug/php-5.4.11/Zend/zend_hash.c:804 #9 shutdown_executor at /usr/src/debug/php-5.4.11/Zend/zend_execute_API.c:305 #10 zend_deactivate at /usr/src/debug/php-5.4.11/Zend/zend.c:938 Potential duplicate: bug 886841
Created attachment 685073 [details] File: backtrace
Created attachment 685074 [details] File: build_ids
Created attachment 685075 [details] File: cgroup
Created attachment 685076 [details] File: core_backtrace
Created attachment 685077 [details] File: dso_list
Created attachment 685078 [details] File: environ
Created attachment 685079 [details] File: limits
Created attachment 685081 [details] File: maps
Created attachment 685083 [details] File: open_fds
Created attachment 685085 [details] File: proc_pid_status
Created attachment 685087 [details] File: smolt_data
Created attachment 685089 [details] File: var_log_messages
*** Bug 902706 has been marked as a duplicate of this bug. ***
@Christof: can you confirm if this segfault occurs in previous version (<= 5.4.9) I suspect a regression introduced in 5.4.10, with the fix for upstream bug #63635 (Segfault in gc_collect_cycles). To avoid any mistake, can you also reproduce it without most extension currently enabled (not required by unit test) disable (especially: apc and xdebug) ?
Created attachment 686607 [details] backtrace with most pecl extensions disabled
I also tried various combinations with apc and xdebug enabled / disabled. They all crash eventually.
Can you please give a try to this scratch build: http://koji.fedoraproject.org/koji/taskinfo?taskID=4908461 This is exactly version 5.4.11 + patch for PHP bug 63535 reverted. Notice : please download the RPM asap, as scratch build resuts are not kept online for a long time.
Created attachment 689730 [details] Tested with php-5.4.11-1.fc18.0.1.x86_64.rpm
Thanks for the test. So obviously this is not related to the fix. Could you please report this upstream, to have is managed by a gc expert (above my current skill) ? Or do you prefer I report it ?
If you could do it that would be nice. The PHP bug tracker is a bit to hostile for my taste. The whole thing is also really difficult to reproduce. Sometimes it takes eight tries until it crashes.
Reported upstream as https://bugs.php.net/64111 A simple reproducer will be welcome (probably not simple to find) for gc issue, waiting for a real fix, some workaround could "reduce" crash: - increase memory_limit (to avoid gc run) - disable gc (zend.enable_gc), warning, this can requires much more memory
I have tried with enable_gc = Off and I still get crashes in a gc related function (top of the backtrace): gc_remove_zval_from_buffer _zval_ptr_dtor zend_hash_destroy zend_object_std_dtor zend_objects_free_object_storage zend_objects_store_del_ref_by_handle_ex zend_objects_store_del_ref _zval_ptr_dtor zend_hash_destroy _zval_dtor_func _zval_ptr_dtor zend_object_std_dtor zend_objects_free_object_storage zend_objects_store_del_ref_by_handle_ex zend_objects_store_del_ref I am also not running out of memory even with gc disabled. As far as I can remember this has started with phpunit 3.7 .
@Christof: the bug was reported against 5.4.11, does the crash still occurs with latest PHP (5.4.14 from testing) ? Can you provide a new backtrace, and, if possible, a coredump ?
(In reply to comment #23) > @Christof: the bug was reported against 5.4.11, does the crash still occurs > with latest PHP (5.4.14 from testing) ? > > Can you provide a new backtrace, and, if possible, a coredump ? I haven't seen it for a while, though that might be due to me disabling some extensions. I will try to trigger it.
(In reply to comment #24) > (In reply to comment #23) > > @Christof: the bug was reported against 5.4.11, does the crash still occurs > > with latest PHP (5.4.14 from testing) ? > > > > Can you provide a new backtrace, and, if possible, a coredump ? > > I haven't seen it for a while, though that might be due to me disabling some > extensions. I will try to trigger it. I can't reproduce it with 5.4.13, even with apc & xdebug enabled.