Red Hat Bugzilla – Bug 139542
egroupware triggers PHP crashes at request shutdown
Last modified: 2007-11-30 17:07:05 EST
Description of problem:
Tracker bug for segfaults in PHP triggered by egroupware.org.
Version-Release number of selected component (if applicable):
Two backtraces which look from php_request_shutdown have been
obtained, which both look like memory corruption:
#0 0x0081e4cf in malloc_consolidate () from /lib/tls/libc.so.6
#1 0x0081e378 in _int_free () from /lib/tls/libc.so.6
#2 0x0081cff8 in free () from /lib/tls/libc.so.6
#3 0x011102af in shutdown_memory_manager (silent=1, clean_cache=0)
#4 0x010f2e94 in php_request_shutdown (dummy=0x0) at
#5 0x01132993 in php_apache_request_dtor (f=0x8990dd0)
#6 0x01132bf8 in php_output_filter (f=0x8990dd0, bb=0x8b33128)
#7 0x0807483c in ap_pass_brigade (next=0x8e1800, bb=0x9c2be10)
#8 0x0807c489 in default_handler (r=0x8a80508) at
this is being triggered from the same request each time, it appears:
(gdb) print r->the_request
$2 = 0x8f7e408 "GET
Ralf, Can you comment on the egroupware code in question?
Not sure what you want to know about the code.
It's generates InfoLog's main listing:
- it fetches some data from the db
- pases it together with a template to the eTemplate class
- which displays it
The problem is the bug does not happen all the time, then we could add
some debug code to see in which parts it fails.
I'm not an expert on php's internal flow: Is the above call-stack what
usualy happens when php shuts down at the end of a script?
Did you find a workaround for this Matt or is it still an issue?
as far as I know, this does not longer happen.
I dont know what has been changed, I only know it was not on the eGroupWare side.
This bug is filed against RHEL 3, which is in maintenance phase.
During the maintenance phase, only security errata and select mission
critical bug fixes will be released for enterprise products. Since
this bug does not meet that criteria, it is now being closed.
For more information of the RHEL errata support policy, please visit:
If you feel this bug is indeed mission critical, please contact your
support representative. You may be asked to provide detailed
information on how this bug is affecting you.