ID: 40479
Comment by: chris at crgs 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:
Hi,
Just to echo the previous comment, I have experienced the same crash
with PHP 5.2.9-2 under Win32 (Server 2003 R2), when upgrading the MySQL
DLLs from 5.0.77 to 5.1.34. I am bypassing the copy of libmysql.dll
provided with PHP in order to work around another bug, and I found that
when I upgraded to libmysql.dll 5.1.34, PHP crashed out with the
'zend_mm_heap corrupted' error when running certain scripts (especially
ones that access MySQL, like phpMyAdmin), which in turn caused IIS to
error out with 'CGI Error: The specified CGI application misbehaved by
not returning a complete set of HTTP headers.'
The issue is resolved if I copy libmysql.dll version 5.0.77 into my PHP
path, which indicates that this may be one of the causes of the
problem.
I can reproduce this bug reliably.
Previous Comments:
------------------------------------------------------------------------
[2009-04-29 17:30:49] jesse at eonstreet dot com
Hello,
I too have been able to recreate this bug with php 5.2.9
It occurrs when UPGRADING from Mysql 5.0.45 x64 el5 to Mysql 5.1.x x64
el5. (mysql 5.1.25 5.1.30 5.1.33 5.1.34
The error occurrs when I recompile PHP against the new Mysql-devel
5.1.x header files.
I've tried compiling against the native PHP mysql libraries and also
specifying the mysql libraries in /usr.
I believe that the heap error occurrs due to a debug necesity becuase I
followed the advice of a previous comment(THANK YOU!!!!) I placed
enable-debug in the configure command and IT WORKS!
I can't pin it down for sure but there is some incompatibility with
mysql 5.1.x and the php-mysql extension that calls a function from the
debug extension.
I think the solution lies in checking the mysql extension in PHP and
finding where the debug function is called and only calling with the
debug extension enabled / loaded.
------------------------------------------------------------------------
[2009-03-20 09:27:23] wilfried dot loche at fr dot adp dot com
Hello,
This is the first time I see exactly the same message you all have.
You may use an accelerator (such as eAccelerator, I saw many results
for this error on their forums).
Personally, I try to use the Zend Accelerator and Loader provided by
the Zend Platform 3.6.2 and it fails (Fatal Error on accessing an object
as an array... although it implements the ArrayAccess!). Yesterday
evening, I tried to blacklist the supposed 'bad' file and got the famous
error 'zend_mm_heap corrupted' :)
I soon as I disable the 'Code Acceleration', I got no troubles. It
seems it's not due to the PHP Core, but maybe a change on it that has
broken the third party accelerators...
Voila :),
Wilfried Loche
------------------------------------------------------------------------
[2009-03-18 09:25:20] dwdkl dot pub at o2 dot pl
Apache 2.0.x - problem does not occur.
------------------------------------------------------------------------
[2009-03-13 10:57:32] dwdkl dot pub at o2 dot pl
I have this problem too.
Configuration: PHP 5.2.8 (Win32), Apache 2.2.11, MySQL 5.1.31, OS
WinXP.
I have this bug, when i try run phpmyadmin (all versions). Apache
restarted and i found in apache's logs the message "zend_mm_heap
corrupted".
Sorry, my english is weak ;-)
------------------------------------------------------------------------
[2009-03-12 08:32:43] john dot glazebrook at guava dot com
I'm surprised this isn't being talked about more. I see it
occasionally, and I am using Zend Framework. Why don't other people
using ZF see it?
------------------------------------------------------------------------
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
