#18044 [Com]: apache child segfaults on page using sessions

From: Date: Wed, 14 Aug 2002 21:38:36 +0000
Subject: #18044 [Com]: apache child segfaults on page using sessions
References: 1  Groups: php.bugs 
Request: Send a blank email to php-bugs+get-16835@lists.php.net to get a copy of this message
ID: 18044 Comment by: darkfire@yourmojo.com Reported By: mgriego@utdallas.edu Status: Feedback Bug Type: Session related Operating System: RedHat Linux 7.2 PHP Version: 4.2.1 New Comment: I am also not using the Zend Optimizer. Trying out snapshot 'php4-200208130900'. I'll let you know what happens. Previous Comments: ------------------------------------------------------------------------ [2002-08-14 12:34:44] glerma@dal.dset.com I also wanted to point out that I'm not using Zend Optimizer as mgriego. I had opened a new ticket on this, but was told to use this ticket as a reference. I hope to stimulate more discusstion on this.Is there anything that can be seen with the backtrace I provided, or is more tracing needed???? ------------------------------------------------------------------------ [2002-08-13 19:40:49] glerma@dal.dset.com I'm having similar problem. Here is a backtrace of my Apache Core file. I had originally reported to bugzilla.apache.org, but they referred the backtrace to php. Basically, the systems are the same as mgriego's. Seg Faults occur after about a day or sometimes even several hours of running apache w/PHP 4.2.2 parsed-pages. Here are my build specs: I am using the following components with Apache Web Server 1.3.26 on a Solaris 9 platform: openssl-engine-0.9.6d mm-1.1.3 mod_ssl-2.8.10-1.3.26 php-4.2.2 I will also include backtrace given to apache dudes: Output from gdb backtrace: #0 ps_mm_destroy (data=0x1091b8) at mod_mm.c:241 #1 0xfeca8348 in zm_shutdown_ps_mm (type=0, module_number=10) at mod_mm.c:293 #2 0xfec56eac in module_destructor (module=0x113650) at zend_API.c:1127 #3 0xfec59014 in zend_hash_destroy (ht=0xfed6ee7c) at zend_hash.c:541 #4 0xfec53d98 in zend_shutdown () at zend.c:490 #5 0xfec6289c in php_module_shutdown () at main.c:1050 #6 0xfec6284c in php_module_shutdown_wrapper (sapi_globals=0x0) at main.c:1027 #7 0xfec5fd48 in apache_php_module_shutdown_wrapper () at mod_php4.c:795 #8 0x1a9f0 in run_cleanups () #9 0x1825c in ap_clear_pool () #10 0x182f0 in ap_destroy_pool () #11 0x18244 in ap_clear_pool () #12 0x182f0 in ap_destroy_pool () #13 0x2e9c8 in clean_parent_exit () #14 0x32a7c in standalone_main () #15 0x33278 in main () I would like to further investigation of this problem. Seems maybe to me mm-releted to me at this point. I too am using sessions (session_start()) If more tracing is needed, please reply. THanks -George ------------------------------------------------------------------------ [2002-08-13 12:47:38] rasmus@php.net Does it happen with Zend Optimizer turned off? ------------------------------------------------------------------------ [2002-08-13 12:46:06] darkfire@yourmojo.com I am using the snapshot "php4-200207240900". And this problem is still occurring. This is an extremely serious bug. I have to restart Apache every 2 to 3 days. Please look into this. ------------------------------------------------------------------------ [2002-07-17 11:36:32] sniper@php.net Try this snapshot: http://snaps.php.net/php4-latest.tar.gz ------------------------------------------------------------------------ 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 http://bugs.php.net/18044 -- Edit this bug report at http://bugs.php.net/?id=18044&edit=1

« previous php.bugs (#16835) next »