ID: 40479
Comment by: sriram dot natarajan at gmail dot com
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:
to answer tdikarim at hotmail dot com's question, you can probably add
set USE_ZEND_ALLOC=0 within your apachectl.bat under your apache
installation directory /bin. not, for this to work, you should start
apache from command line and not as a 'service'. also, may I suggest
that you probably try to run with php 5.2.10 or php 5.3 (from
windows.php.net) and see if you are able to reproduce this issue
before you consider using the work around (using USE_ZEND_ALLOC).
please note that using USE_ZEND_ALLOC=0 will have some performance
penalty.
now, looking closely into this bug, as Rasmus mentioned earler, this
bug has become a catch-all for memory corruption.
looking at the some of the stack traces and with so many people have
reported this , this is probably a valid bug and we would love to fix
this issue provided some one can provide us a script (even if it is
complicated) that any one of us can reproduce. this would quickly help
us to get to a solution.
some of the folks have mentioned that they use redhat / fedora but
have failed to mention whether they are using php with apache's pre-
fork (which is fortunately the default )mpm or worker mpm .
(note: if you don't know what is worker mpm, you are most likely using
the default pre-fork mpm !).
why is this important ? - this is because if you are running your
apache in threaded mode but if php is not compiled with 'thread-
safety' option, then one can run into lot of weird race condition. but
with pre-fork apache, you very rarely run into a race condition.
so, please when you report this crash, please provide us the php
version and is it compiled with ZTS (zend thread safety) enabled and
is your web server multi-threaded. for example, you can get apache's
server information by running 'httpd -V' from your linux box.
Previous Comments:
------------------------------------------------------------------------
[2009-09-17 15:32:34] tdikarim at hotmail dot com
Hi all,
Someone have the solution for os windows XP
thanks
------------------------------------------------------------------------
[2009-08-10 20:53:45] asilentpenguin at yahoo dot com
On Fedora / centOS
edit:
/usr/local/apache2/bin/apachectl
and add:
export USE_ZEND_ALLOC=0
and stop & start apache.
P.S.: i think you are underestimating the number of occurences for this
bug and, as so, the frustration amongst PHP developers
------------------------------------------------------------------------
[2009-07-30 06:22:49] laurynas dot butkus at gmail dot com
Finnally, found solution on Ubuntu Hardy.
Add line:
export USE_ZEND_ALLOC=0
to file:
/etc/apache2/envvars
and restart apache... Crashing stopped.
------------------------------------------------------------------------
[2009-06-24 23:31:17] rasmus@php.net
This has turned into a catch-all bug report for any generic memory
corruption, not even necessarily in PHP itself. It could be a 3rd-party
library stomping on memory as shown by some of the reports of things
going away when upgrading a lib. As a single bug report it isn't of
much use to us, but the backtraces to help and might point us to an
actual problem in PHP.
------------------------------------------------------------------------
[2009-06-24 23:14:03] BAReFOOt at mailinator dot com
Well, I we mysql, the installed webapp (mediawiki) is not using it,
it's version 5.0.70, we got the debug extension enabled, and we still
get the bug.
It crashes the whole apache (2.2.11) instance! We don't have any
special PHP extensions on it.
But frankly, by knowing the quality of the Zend engine code itself, I
do not have any hopes that there is anyone who works on that code, and
is even remotely able to fix this. :P
I recommend switching to a real language, and stop using this
VisualBasic of web languages. :/
Sorry, after all this time, (255 days, or 8.5 months!), I have no good
words for this anymore. It basically makes PHP useless, and any new PHP
development (webapps), are now completely out of question in our
company.
------------------------------------------------------------------------
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