Bug #62929 [Opn]: Segmentation fault on Zend Framework application
Edit report at https://bugs.php.net/bug.php?id=62929&edit=1
ID: 62929
Updated by: larue...@php.net
Reported by:sergiu dot ionescu at gmail dot com
Summary:Segmentation fault on Zend Framework application
Status: Open
Type: Bug
Package:*General Issues
Operating System: Ubuntu 10.04.4 LTS
PHP Version:PHP 5.3.16
Block user comment: N
Private report: N
New Comment:
so, this is related to apc?
Previous Comments:
[2012-08-30 16:13:15] sergiu dot ionescu at gmail dot com
Setting apc.enable_cli=0 so far has eliminated the issue.
I don't this fixed the underlying issue but at least it gets rid of the nasty
exit code at the end on the script.
[2012-08-28 08:04:19] larue...@php.net
if I don't get a script to reproduce it, then I think,, I can do nothing..
since
there is not much info can get from the backtrace
[2012-08-28 07:02:45] sergiu dot ionescu at gmail dot com
I could, but i think it won't help much. As i stated initially it's a cli
script form a Magento/ZF application with quite a few contributed modules.
If i can get to a one file script that produces the error i will post it.
Is there anything else you can do while you don't have that?
[2012-08-28 02:47:44] larue...@php.net
could you give us a reproducable script, or scripts? thanks, :)
[2012-08-27 16:15:38] sergiu dot ionescu at gmail dot com
After updating all the extensions i still get the same thing.
I extra detail i can provide is that i occasionally get
zend_mm_heap corrupted
instead of segmentation fault
and the line where the segfault occurs is the condition line from:
#if ZEND_MM_SAFE_UNLINKING
if (UNEXPECTED(prev->next_free_block != mm_block) ||
UNEXPECTED(next->prev_free_block != mm_block)) {
zend_mm_panic("zend_mm_heap corrupted");
}
#endif
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=62929
--
Edit this bug report at https://bugs.php.net/bug.php?id=62929&edit=1
Bug #62929 [Opn]: Segmentation fault on Zend Framework application
Edit report at https://bugs.php.net/bug.php?id=62929&edit=1
ID: 62929
Updated by: larue...@php.net
Reported by:sergiu dot ionescu at gmail dot com
Summary:Segmentation fault on Zend Framework application
Status: Open
Type: Bug
Package:*General Issues
Operating System: Ubuntu 10.04.4 LTS
PHP Version:PHP 5.3.16
Block user comment: N
Private report: N
New Comment:
if I don't get a script to reproduce it, then I think,, I can do nothing..
since
there is not much info can get from the backtrace
Previous Comments:
[2012-08-28 07:02:45] sergiu dot ionescu at gmail dot com
I could, but i think it won't help much. As i stated initially it's a cli
script form a Magento/ZF application with quite a few contributed modules.
If i can get to a one file script that produces the error i will post it.
Is there anything else you can do while you don't have that?
[2012-08-28 02:47:44] larue...@php.net
could you give us a reproducable script, or scripts? thanks, :)
[2012-08-27 16:15:38] sergiu dot ionescu at gmail dot com
After updating all the extensions i still get the same thing.
I extra detail i can provide is that i occasionally get
zend_mm_heap corrupted
instead of segmentation fault
and the line where the segfault occurs is the condition line from:
#if ZEND_MM_SAFE_UNLINKING
if (UNEXPECTED(prev->next_free_block != mm_block) ||
UNEXPECTED(next->prev_free_block != mm_block)) {
zend_mm_panic("zend_mm_heap corrupted");
}
#endif
[2012-08-27 14:55:12] sergiu dot ionescu at gmail dot com
Hello,
I have compiled PHP 5.3.16(http://kr.php.net/get/php-5.3.16.tar.bz2) and i am
experiencing similar issues.
The new back-trace is:
[Thread debugging using libthread_db enabled]
Program received signal SIGSEGV, Segmentation fault.
0x0068a7fb in zend_mm_remove_from_free_list (heap=0xe73290,
mm_block=0x2ee4168) at /home/vagrant/php-5.3.16/Zend/zend_alloc.c:845
845 if (UNEXPECTED(prev->next_free_block != mm_block) ||
UNEXPECTED(next->prev_free_block != mm_block)) {
(gdb) bt
#0 0x0068a7fb in zend_mm_remove_from_free_list (heap=0xe73290,
mm_block=0x2ee4168) at /home/vagrant/php-5.3.16/Zend/zend_alloc.c:845
#1 0x0068a9ab in _zend_mm_free_int (heap=0xe73290, p=0x2ee4128) at
/home/vagrant/php-5.3.16/Zend/zend_alloc.c:2029
#2 0x0069fcd0 in destroy_zend_class (pce=) at
/home/vagrant/php-5.3.16/Zend/zend_opcode.c:187
#3 0x006b43d5 in zend_hash_apply_deleter (ht=0xe73be0, p=0x142dda0) at
/home/vagrant/php-5.3.16/Zend/zend_hash.c:612
#4 0x006b44e9 in zend_hash_reverse_apply (ht=0xe73be0,
apply_func=0x69aed0 ) at
/home/vagrant/php-5.3.16/Zend/zend_hash.c:762
#5 0x0069bbbe in shutdown_executor () at
/home/vagrant/php-5.3.16/Zend/zend_execute_API.c:312
#6 0x006a85c2 in zend_deactivate () at
/home/vagrant/php-5.3.16/Zend/zend.c:891
#7 0x00654305 in php_request_shutdown (dummy=) at
/home/vagrant/php-5.3.16/main/main.c:1661
#8 0x00733dfa in main (argc=, argv=) at /home/vagrant/php-5.3.16/sapi/cli/php_cli.c:1368
I am still using some on the old php5.3.2 extensions but i am upgrading the one
by one - just in case i catch the culprit.
Please let me know if i can provide additional details.
Thanks.
[2012-08-26 05:54:15] ras...@php.net
There is no changelog entry for it. Your report is not specific enough, but we
need to know if it is happening in a current version before we bother spending
any time looking for it. chasing fixed bugs isn't the best use of our time.
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=62929
--
Edit this bug report at https://bugs.php.net/bug.php?id=62929&edit=1
Bug #62929 [Opn]: Segmentation fault on Zend Framework application
Edit report at https://bugs.php.net/bug.php?id=62929&edit=1
ID: 62929
Updated by: larue...@php.net
Reported by:sergiu dot ionescu at gmail dot com
Summary:Segmentation fault on Zend Framework application
Status: Open
Type: Bug
Package:*General Issues
Operating System: Ubuntu 10.04.4 LTS
PHP Version:PHP 5.3.16
Block user comment: N
Private report: N
New Comment:
could you give us a reproducable script, or scripts? thanks, :)
Previous Comments:
[2012-08-27 16:15:38] sergiu dot ionescu at gmail dot com
After updating all the extensions i still get the same thing.
I extra detail i can provide is that i occasionally get
zend_mm_heap corrupted
instead of segmentation fault
and the line where the segfault occurs is the condition line from:
#if ZEND_MM_SAFE_UNLINKING
if (UNEXPECTED(prev->next_free_block != mm_block) ||
UNEXPECTED(next->prev_free_block != mm_block)) {
zend_mm_panic("zend_mm_heap corrupted");
}
#endif
[2012-08-27 14:55:12] sergiu dot ionescu at gmail dot com
Hello,
I have compiled PHP 5.3.16(http://kr.php.net/get/php-5.3.16.tar.bz2) and i am
experiencing similar issues.
The new back-trace is:
[Thread debugging using libthread_db enabled]
Program received signal SIGSEGV, Segmentation fault.
0x0068a7fb in zend_mm_remove_from_free_list (heap=0xe73290,
mm_block=0x2ee4168) at /home/vagrant/php-5.3.16/Zend/zend_alloc.c:845
845 if (UNEXPECTED(prev->next_free_block != mm_block) ||
UNEXPECTED(next->prev_free_block != mm_block)) {
(gdb) bt
#0 0x0068a7fb in zend_mm_remove_from_free_list (heap=0xe73290,
mm_block=0x2ee4168) at /home/vagrant/php-5.3.16/Zend/zend_alloc.c:845
#1 0x0068a9ab in _zend_mm_free_int (heap=0xe73290, p=0x2ee4128) at
/home/vagrant/php-5.3.16/Zend/zend_alloc.c:2029
#2 0x0069fcd0 in destroy_zend_class (pce=) at
/home/vagrant/php-5.3.16/Zend/zend_opcode.c:187
#3 0x006b43d5 in zend_hash_apply_deleter (ht=0xe73be0, p=0x142dda0) at
/home/vagrant/php-5.3.16/Zend/zend_hash.c:612
#4 0x006b44e9 in zend_hash_reverse_apply (ht=0xe73be0,
apply_func=0x69aed0 ) at
/home/vagrant/php-5.3.16/Zend/zend_hash.c:762
#5 0x0069bbbe in shutdown_executor () at
/home/vagrant/php-5.3.16/Zend/zend_execute_API.c:312
#6 0x006a85c2 in zend_deactivate () at
/home/vagrant/php-5.3.16/Zend/zend.c:891
#7 0x00654305 in php_request_shutdown (dummy=) at
/home/vagrant/php-5.3.16/main/main.c:1661
#8 0x00733dfa in main (argc=, argv=) at /home/vagrant/php-5.3.16/sapi/cli/php_cli.c:1368
I am still using some on the old php5.3.2 extensions but i am upgrading the one
by one - just in case i catch the culprit.
Please let me know if i can provide additional details.
Thanks.
[2012-08-26 05:54:15] ras...@php.net
There is no changelog entry for it. Your report is not specific enough, but we
need to know if it is happening in a current version before we bother spending
any time looking for it. chasing fixed bugs isn't the best use of our time.
[2012-08-26 05:26:02] sergiu dot ionescu at gmail dot com
Can you please point me to the change-log note for this fix?
I want to be 100% sure that it's the same issue, as we are trying to be as
conservative as possible with environment updates.
Thanks!
[2012-08-25 17:42:42] ras...@php.net
Ah, I see the version at the bottom of your report now. I have fixed it in the
report. 5.3.2 is from March 2010. Please upgrade to something more recent.
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=62929
--
Edit this bug report at https://bugs.php.net/bug.php?id=62929&edit=1
Bug #62929 [Opn]: Segmentation fault on Zend Framework application
Edit report at https://bugs.php.net/bug.php?id=62929&edit=1
ID: 62929
User updated by:sergiu dot ionescu at gmail dot com
Reported by:sergiu dot ionescu at gmail dot com
Summary:Segmentation fault on Zend Framework application
Status: Open
Type: Bug
Package:*General Issues
Operating System: Ubuntu 10.04.4 LTS
-PHP Version:PHP 5.3.2
+PHP Version:PHP 5.3.16
Block user comment: N
Private report: N
New Comment:
Hello,
I have compiled PHP 5.3.16(http://kr.php.net/get/php-5.3.16.tar.bz2) and i am
experiencing similar issues.
The new back-trace is:
[Thread debugging using libthread_db enabled]
Program received signal SIGSEGV, Segmentation fault.
0x0068a7fb in zend_mm_remove_from_free_list (heap=0xe73290,
mm_block=0x2ee4168) at /home/vagrant/php-5.3.16/Zend/zend_alloc.c:845
845 if (UNEXPECTED(prev->next_free_block != mm_block) ||
UNEXPECTED(next->prev_free_block != mm_block)) {
(gdb) bt
#0 0x0068a7fb in zend_mm_remove_from_free_list (heap=0xe73290,
mm_block=0x2ee4168) at /home/vagrant/php-5.3.16/Zend/zend_alloc.c:845
#1 0x0068a9ab in _zend_mm_free_int (heap=0xe73290, p=0x2ee4128) at
/home/vagrant/php-5.3.16/Zend/zend_alloc.c:2029
#2 0x0069fcd0 in destroy_zend_class (pce=) at
/home/vagrant/php-5.3.16/Zend/zend_opcode.c:187
#3 0x006b43d5 in zend_hash_apply_deleter (ht=0xe73be0, p=0x142dda0) at
/home/vagrant/php-5.3.16/Zend/zend_hash.c:612
#4 0x006b44e9 in zend_hash_reverse_apply (ht=0xe73be0,
apply_func=0x69aed0 ) at
/home/vagrant/php-5.3.16/Zend/zend_hash.c:762
#5 0x0069bbbe in shutdown_executor () at
/home/vagrant/php-5.3.16/Zend/zend_execute_API.c:312
#6 0x006a85c2 in zend_deactivate () at
/home/vagrant/php-5.3.16/Zend/zend.c:891
#7 0x00654305 in php_request_shutdown (dummy=) at
/home/vagrant/php-5.3.16/main/main.c:1661
#8 0x00733dfa in main (argc=, argv=) at /home/vagrant/php-5.3.16/sapi/cli/php_cli.c:1368
I am still using some on the old php5.3.2 extensions but i am upgrading the one
by one - just in case i catch the culprit.
Please let me know if i can provide additional details.
Thanks.
Previous Comments:
[2012-08-26 05:54:15] ras...@php.net
There is no changelog entry for it. Your report is not specific enough, but we
need to know if it is happening in a current version before we bother spending
any time looking for it. chasing fixed bugs isn't the best use of our time.
[2012-08-26 05:26:02] sergiu dot ionescu at gmail dot com
Can you please point me to the change-log note for this fix?
I want to be 100% sure that it's the same issue, as we are trying to be as
conservative as possible with environment updates.
Thanks!
[2012-08-25 17:42:42] ras...@php.net
Ah, I see the version at the bottom of your report now. I have fixed it in the
report. 5.3.2 is from March 2010. Please upgrade to something more recent.
[2012-08-25 17:41:00] ras...@php.net
The PHP version is not irrelevant at all. We can't possibly do anything with
this
bug unless you tell us which version you are seeing it in.
[2012-08-25 17:33:11] sergiu dot ionescu at gmail dot com
Description:
I randomly get segmentation faults while running cli scripts.
The fault occurs at the end of the script run and happens in more than 50% of
the cases.
Expected result:
No seg fault.
Actual result:
--
syslog: [24766.653698] php[8084]: segfault at 30 ip 006b7241 sp
7fff508cc110 error 4 in php5[40+70e000]
The GDB backtrace is:
#0 0x006b7241 in ?? ()
#1 0x006b771b in ?? ()
#2 0x006a3a38 in zend_hash_destroy ()
#3 0x00696a3f in _zval_dtor_func ()
#4 0x0068aa9d in _zval_ptr_dtor ()
#5 0x006a3a38 in zend_hash_destroy ()
#6 0x00696a3f in _zval_dtor_func ()
#7 0x0068aa9d in _zval_ptr_dtor ()
#8 0x006a3a38 in zend_hash_destroy ()
#9 0x00696a3f in _zval_dtor_func ()
#10 0x0068aa9d in _zval_ptr_dtor ()
#11 0x006a3a38 in zend_hash_destroy ()
#12 0x006b8a89 in zend_object_std_dtor ()
#13 0x006b8aa9 in zend_objects_free_object_storage ()
#14 0x006bc16c in zend_objects_store_free_object_storage ()
#15 0x0068ae95 in ?? ()
#16 0x00697782 in ?? ()
#17 0x00643165 in php_request_shutdown ()
#18 0x007273e4 in ?? ()
#19 0x752a5c4d in __libc_start_main (main=,
argc=, ubp_av=, init=,
fini=, rtld_fini=,
stack_end=0x7fffe6a8)
a
Bug #62929 [Opn]: Segmentation fault on Zend Framework application
Edit report at https://bugs.php.net/bug.php?id=62929&edit=1 ID: 62929 Updated by: ras...@php.net Reported by:sergiu dot ionescu at gmail dot com Summary:Segmentation fault on Zend Framework application Status: Open Type: Bug Package:*General Issues Operating System: Ubuntu 10.04.4 LTS PHP Version:PHP 5.3.2 Block user comment: N Private report: N New Comment: There is no changelog entry for it. Your report is not specific enough, but we need to know if it is happening in a current version before we bother spending any time looking for it. chasing fixed bugs isn't the best use of our time. Previous Comments: [2012-08-26 05:26:02] sergiu dot ionescu at gmail dot com Can you please point me to the change-log note for this fix? I want to be 100% sure that it's the same issue, as we are trying to be as conservative as possible with environment updates. Thanks! [2012-08-25 17:42:42] ras...@php.net Ah, I see the version at the bottom of your report now. I have fixed it in the report. 5.3.2 is from March 2010. Please upgrade to something more recent. [2012-08-25 17:41:00] ras...@php.net The PHP version is not irrelevant at all. We can't possibly do anything with this bug unless you tell us which version you are seeing it in. [2012-08-25 17:33:11] sergiu dot ionescu at gmail dot com Description: I randomly get segmentation faults while running cli scripts. The fault occurs at the end of the script run and happens in more than 50% of the cases. Expected result: No seg fault. Actual result: -- syslog: [24766.653698] php[8084]: segfault at 30 ip 006b7241 sp 7fff508cc110 error 4 in php5[40+70e000] The GDB backtrace is: #0 0x006b7241 in ?? () #1 0x006b771b in ?? () #2 0x006a3a38 in zend_hash_destroy () #3 0x00696a3f in _zval_dtor_func () #4 0x0068aa9d in _zval_ptr_dtor () #5 0x006a3a38 in zend_hash_destroy () #6 0x00696a3f in _zval_dtor_func () #7 0x0068aa9d in _zval_ptr_dtor () #8 0x006a3a38 in zend_hash_destroy () #9 0x00696a3f in _zval_dtor_func () #10 0x0068aa9d in _zval_ptr_dtor () #11 0x006a3a38 in zend_hash_destroy () #12 0x006b8a89 in zend_object_std_dtor () #13 0x006b8aa9 in zend_objects_free_object_storage () #14 0x006bc16c in zend_objects_store_free_object_storage () #15 0x0068ae95 in ?? () #16 0x00697782 in ?? () #17 0x00643165 in php_request_shutdown () #18 0x007273e4 in ?? () #19 0x752a5c4d in __libc_start_main (main=, argc=, ubp_av=, init=, fini=, rtld_fini=, stack_end=0x7fffe6a8) at libc-start.c:226 #20 0x0042c6f9 in _start () The php version i am running is PHP 5.3.2-1ubuntu4.17 with Suhosin-Patch (cli) (built: Jun 19 2012 03:21:35). What is your recommendation. Thanks. -- Edit this bug report at https://bugs.php.net/bug.php?id=62929&edit=1
