#20985 [Opn->Fbk]: heavy load = Segmentation fault

ID: 20985 Updated by: iliaa@php.net Reported By: jfl@eksperten.dk -Status: Open +Status: Feedback Bug Type: Reproducible crash Operating System: Redhat Linux 7.3 & 8 PHP Version: 4.3.0RC3 New Comment: I appreciate your offer, but it would be much better if you could narrow down the problem. There is just too much code to go over. Previous Comments: ------------------------------------------------------------------------ [2002-12-16 07:42:09] jfl@eksperten.dk I can give you access to the system. Would you like that? I have also sent an email to iliaa@php.net regarding this. ------------------------------------------------------------------------ [2002-12-15 21:34:42] iliaa@php.net This is a fairly big script and I cannot even run it fully because I am missing over a dosen various includes your script requires. Is there any way you could reduce this to a single, preferably short script that could be used to replicate the memory leak you are seeing? ------------------------------------------------------------------------ [2002-12-15 13:21:15] jfl@eksperten.dk The files has been sent to iliaa@php.net. If none of my scripts has errors I can not get SIGSEGV. But I get "Last leak repeated X times". Have a look at http://test.webalogic.net/bugs/error_log-no_SIGSEGV and the other files at http://test.webalogic.net/ ------------------------------------------------------------------------ [2002-12-14 23:37:19] iliaa@php.net Could you provide copies of the list.phtml & info.phtml scripts? ------------------------------------------------------------------------ [2002-12-14 16:22:39] jfl@eksperten.dk By starting Apache, with built in Php-4.3.0RC3, with 'gdb /usr/local/apache/bin/httpd' I can not make it crash. But if I start Apache normally I get a Segmentation fault in the error_log. Please see the bottom of http://test.webalogic.net/bugs/error_log_php4-3 (2mb) What can I do to help you further? ------------------------------------------------------------------------ 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/20985 -- Edit this bug report at http://bugs.php.net/?id=20985&edit=1