Bug #67254 [Fbk->NoF]: PHP crashes in zend_stack_push

From: Date: Sun, 01 Mar 2015 04:22:19 +0000
Subject: Bug #67254 [Fbk->NoF]: PHP crashes in zend_stack_push
References: 1  Groups: php.bugs 
Request: Send a blank email to php-bugs+get-191019@lists.php.net to get a copy of this message
Edit report at https://bugs.php.net/bug.php?id=67254&edit=1 ID: 67254 Updated by: php-bugs@lists.php.net Reported by: majo-bugs dot php dot net at pematon dot com Summary: PHP crashes in zend_stack_push -Status: Feedback +Status: No Feedback Type: Bug Package: Reproducible crash Operating System: FreeBSD 9.2-RELEASE-p5 PHP Version: 5.5.19 Private report: N New Comment: No feedback was provided. The bug is being suspended because we assume that you are no longer experiencing the problem. If this is not the case and you are able to provide the information that was requested earlier, please do so and change the status of the bug back to "Re-Opened". Thank you. Previous Comments: ------------------------------------------------------------------------ [2015-02-20 20:16:39] getriebesand at freenet dot de I don't know how. I don't use dtrace. Maybe I have to file a bug report to the maintainer of the package. (I use the default packege for ubuntu 14.04 LTS) then forget my bt and use majo-bugs's bt But this error is hard to reproduce because it only happens on many requests. Bofore I had have opcache enabled and got many fatal error that a function can not be redeclared. But I checked the code many times. Even with require_once and check if function_exists(). Then I disabled opcache and since then I get seg faults. I use Apache mpm-prefork and have tried to use different configs (reduce MaxConnectionsPerChild...) but it didn't solve anything. ------------------------------------------------------------------------ [2015-02-16 23:44:47] rasmus@php.net getriebesand dtrace? Try it without dtrace. ------------------------------------------------------------------------ [2015-02-16 17:36:08] getriebesand at freenet dot de Same here: Ubuntu 14.04 PHP 5.5.9-1ubuntu4.5 Apache 2.4.7 This happend every few minutes on a php file with highest requests on our server (8 req/sec) #0 0x00007ff0931da97d in zend_stack_push (stack=stack@entry=0x7ff0939a0ca0 <compiler_globals+608>, element=element@entry=0x7ff0939a0c78 <compiler_globals+568>, size=size@entry=40) at /build/buildd/php5-5.5.9+dfsg/Zend/zend_stack.c:42 #1 0x00007ff0931a631e in compile_file (file_handle=file_handle@entry=0x7fffe2adee30, type=2) at Zend/zend_language_scanner.l:586 #2 0x00007ff0931cbafa in dtrace_compile_file (file_handle=0x7fffe2adee30, type=<optimized out>) at /build/buildd/php5-5.5.9+dfsg/Zend/zend_dtrace.c:40 #3 0x00007ff093054cb4 in phar_compile_file (file_handle=<optimized out>, type=<optimized out>) at /build/buildd/php5-5.5.9+dfsg/ext/phar/phar.c:3383 #4 0x00007ff0931dd57f in zend_execute_scripts (type=type@entry=2, retval=retval@entry=0x0, file_count=file_count@entry=1) at /build/buildd/php5-5.5.9+dfsg/Zend/zend.c:1308 #5 0x00007ff09328d4fd in php_handler (r=<optimized out>) at /build/buildd/php5-5.5.9+dfsg/sapi/apache2handler/sapi_apache2.c:669 #6 0x00007ff097b8a680 in ap_run_handler () #7 0x00007ff097b8abc9 in ap_invoke_handler () #8 0x00007ff097ba016a in ap_process_async_request () #9 0x00007ff097ba0444 in ap_process_request () #10 0x00007ff097b9cf02 in ?? () #11 0x00007ff097b93cc0 in ap_run_process_connection () #12 0x00007ff093bad767 in ?? () from /usr/lib/apache2/modules/mod_mpm_prefork.so #13 0x00007ff093bad9a6 in ?? () from /usr/lib/apache2/modules/mod_mpm_prefork.so #14 0x00007ff093bae60e in ?? () from /usr/lib/apache2/modules/mod_mpm_prefork.so #15 0x00007ff097b7169e in ap_run_mpm () #16 0x00007ff097b6ae36 in main () ------------------------------------------------------------------------ [2015-01-04 01:31:27] majo-bugs dot php dot net at pematon dot com The error message is: Program terminated with signal 11, Segmentation fault. ------------------------------------------------------------------------ [2015-01-04 01:23:22] majo-bugs dot php dot net at pematon dot com Trying to re-open. ------------------------------------------------------------------------ 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=67254 -- Edit this bug report at https://bugs.php.net/bug.php?id=67254&edit=1

« previous php.bugs (#191019) next »