#40466 [Opn->Bgs]: zend_mm_heap corruption
| From: | tony2001@php.net | Date: | Thu, 15 Feb 2007 16:07:21 +0000 |
| Subject: | #40466 [Opn->Bgs]: zend_mm_heap corruption | ||
| References: | 1 | Groups: | php.bugs |
| Request: | Send a blank email to php-bugs+get-108988@lists.php.net to get a copy of this message | ||
ID: 40466
Updated by: tony2001@php.net
Reported By: stojmir at on dot net dot mk
-Status: Open
+Status: Bogus
Bug Type: Reproducible crash
Operating System: Linux 2.6.9
PHP Version: 5.2.1
New Comment:
I'm afraid you need to report it to eAccelerator developers, since it's
obviously something related to eAccelerator, not PHP itself.
Previous Comments:
------------------------------------------------------------------------
[2007-02-15 15:59:43] stojmir at on dot net dot mk
I tried the latest CVS snapshot with no success. Removing the
eAccelerator however, helped, but my CPU usage now has trippled.
What do you suggest? Where is this supposed to continue?
------------------------------------------------------------------------
[2007-02-13 18:20:54] tony2001@php.net
Please try using this CVS snapshot:
http://snaps.php.net/php5.2-latest.tar.gz
For Windows:
http://snaps.php.net/win32/php5.2-win32-latest.zip
.. And try the snapshot.
------------------------------------------------------------------------
[2007-02-13 18:18:48] bjori@php.net
You can start with disabling eaccelerator and any other
zend extensions you may have loaded.
------------------------------------------------------------------------
[2007-02-13 18:07:17] stojmir at on dot net dot mk
I really have no idea on how to narrow down the code that could
reproduce the crash. It could be anything from the thousands of lines
of code in Drupal.
Any hints? What else can i do in order to help you guys identify and
resolve this?
------------------------------------------------------------------------
[2007-02-13 17:33:37] tony2001@php.net
Thank you for this bug report. To properly diagnose the problem, we
need a short but complete example script to be able to reproduce
this bug ourselves.
A proper reproducing script starts with <?php and ends with ?>,
is max. 10-20 lines long and does not require any external
resources such as databases, etc. If the script requires a
database to demonstrate the issue, please make sure it creates
all necessary tables, stored procedures etc.
Please avoid embedding huge scripts into the report.
------------------------------------------------------------------------
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/40466
--
Edit this bug report at http://bugs.php.net/?id=40466&edit=1