ID: 40479 Comment by: john dot glazebrook at gauva dot co dot uk Reported By: rrossi at maggioli dot it Status: No Feedback Bug Type: Reproducible crash Operating System: Suse Linux 9.0 PHP Version: 5.2.1 New Comment:
> For me it looks like a hardware problem (dead memory segments), please > use a memory testing tool (e.g. memtest86 [1]) or try to reproduce the > bug on an other computer. Dead memory segments can cause exactly that > sort of problems (corrupted memory, crashes, etc). (See my previous messages posted above...) I just tried my code on a brand new HP server, this time on CentOS 5.2, PHP 5.2.0, MySQLI 5.0.45. I still get seg faults in httpd error logs files. So I don't see how this is a hardware fault. I see this error using the same PHP code on 3 different servers, 2 different operating systems and 2 different MySQL versions. I also changed my tables from MyISAM to InnoDB and *STILL* get seg faults. I use Zend Framework and I have changed DB adapters from Mysqli to PDO_MYSQL, but both cause seg faults. Does that cover everything apart from the PHP version? monk.e.boy Previous Comments: ------------------------------------------------------------------------ [2008-08-17 01:00:00] php-bugs at lists dot php dot net No feedback was provided for this bug for over a week, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open". ------------------------------------------------------------------------ [2008-08-09 16:31:38] [EMAIL PROTECTED] Thank you for this bug report. To properly diagnose the problem, we need a backtrace to see what is happening behind the scenes. To find out how to generate a backtrace, please read http://bugs.php.net/bugs-generating-backtrace.php for *NIX and http://bugs.php.net/bugs-generating-backtrace-win32.php for Win32 Once you have generated a backtrace, please submit it to this bug report and change the status back to "Open". Thank you for helping us make PHP better. Also, all problems reported here have different causes but seems to be triggered when starting to use more memory, and the bug disappears when using less memory, or by changing/commenting a random line in your code. For me it looks like a hardware problem (dead memory segments), please use a memory testing tool (e.g. memtest86 [1]) or try to reproduce the bug on an other computer. Dead memory segments can cause exactly that sort of problems (corrupted memory, crashes, etc). [1] memtest86 http://www.memtest.org/#downiso ------------------------------------------------------------------------ [2008-08-09 09:02:24] tarraccas at burningmoth dot com Concerning my previous statement: I was using output buffering in the included files. I've removed the output buffering and I'm no longer getting the error. ------------------------------------------------------------------------ [2008-08-09 08:01:55] tarraccas at burningmoth dot com I get this error when including files in a loop and trying to execute a loop inside one of those included files. ------------------------------------------------------------------------ [2008-07-23 16:30:15] jumpbackhack at gmail dot com This happens no matter what version, 5.2.1, 5.2.6 and even 5.2.7-dev (snap php5.2-200807220430) How is it possible this many users have this bug, some even can reproduce it consistently, and the developers need backtraces? It seems as though it is a common bug and my guess is many come here looking for a solution, do not find one, figure the zend_mm_heap corrupted is intermittent and hope for a solution soon (they do not post they too have the issue). I will attempt to recompile with debug and get a trace, however, this only occurs on production servers (indicating load/stress related issue when using more memory) and will take a while to get the OK to execute. Running one of the scripts provided below to reproduce the crash does not happen for us on development systems. this bug is over 16 months old and when it happens, it is a whopper, please do not ignore! will be happy to provide any additional information that does not require a recompile/waiting for clearance on production. ------------------------------------------------------------------------ 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/40479 -- Edit this bug report at http://bugs.php.net/?id=40479&edit=1
