Req #43593 [Opn->Fbk]: Impossible to disable Zend Memory Manager in anything other than CLI SAPI
| From: | mike@php.net | Date: | Tue, 01 Oct 2013 11:51:17 +0000 |
| Subject: | Req #43593 [Opn->Fbk]: Impossible to disable Zend Memory Manager in anything other than CLI SAPI | ||
| References: | 1 | Groups: | php.bugs |
| Request: | Send a blank email to php-bugs+get-181877@lists.php.net to get a copy of this message | ||
Edit report at https://bugs.php.net/bug.php?id=43593&edit=1
ID: 43593
Updated by: mike@php.net
Reported by: phajdan dot jr at gmail dot com
Summary: Impossible to disable Zend Memory Manager in
anything other than CLI SAPI
-Status: Open
+Status: Feedback
Type: Feature/Change Request
Package: Compile Failure
Operating System: Linux Gentoo 2007.0
PHP Version: 5.2CVS-2007-12-14
Block user comment: N
Private report: N
New Comment:
Works fine here. What SAPI are you using?
/usr/share/nginx/html$ USE_ZEND_ALLOC=0 PHP_FCGI_CHILDREN=0 php-cgi -b 0:9999
$ curl --progress localhost/info.php | grep "Memory Manager"
<tr><td class="e">Zend Memory Manager </td><td
class="v">disabled </td></tr>
It's really just coming from the environment:
http://lxr.php.net/xref/PHP_TRUNK/Zend/zend_alloc.c#2723
Previous Comments:
------------------------------------------------------------------------
[2008-02-02 09:18:42] phajdan dot jr at gmail dot com
After compiling with that option Zend MM is still enabled, according to phpinfo().
Anyway, it must be possible to somehow disable it, because debug build does it. But it would be not
a good solution to use debug build in production.
Please, please check it yourself, *seriously* - no guessing, not requiring me to check every
opportunity.
------------------------------------------------------------------------
[2008-02-01 22:48:39] jani@php.net
How about --disable-malloc-mm ??
------------------------------------------------------------------------
[2008-01-29 07:06:10] phajdan dot jr at gmail dot com
Well, reproduction script is *not*needed* as it's a PHP configuration setting issue. It is
visible for example in <? phpinfo(); ?> and I gave exact *steps* to reproduce at the
beginning.
Here they are, for convenience:
The goal is to disable the Zend Memory Manager.
Try #1:
1. set USE_ZEND_ALLOC in the environment (/etc/profile)
1a. also tried other ways, like setting it in the Apache config (SetEnv etc)
2. Restart Apache to make sure change takes effect
3. View phpinfo page to see if Zend Memory Manager got disabled
3a. But this way works for the CLI version of PHP (setting env in /etc/profile).
Try #2:
(proven to be futile and ineffective, but anyway)
I tried to recompile PHP with ./configure switches like --disable-zend-memory-manager or
--enable-malloc-mm (some webpages told they will disable Zend MM), but as other developers said in
this report, there are no such compile options.
------------------------------------------------------------------------
[2007-12-17 10:59:06] phajdan dot jr at gmail dot com
So the bug I referred to was http://bugs.php.net/bug.php?id=43397. Curently
it's marked as a duplicate of some other bug, which is now closed because of lack of feedback.
I tried to request reopening my original bug, unfortunately without success.
About setting env var - please note that I tried this method. No go. phpinfo shows that Zend Memory
Manager is enabled. Note that I didn't set it from command line, but had in environment
(something like export USE_ZEND_ALLOC=0; /usr/sbin/httpd ...). But it shouldn't make a
difference.
------------------------------------------------------------------------
[2007-12-17 10:00:38] sniper@php.net
How about you tell us what the crash is you get? (what bug id was the one you reported?) Also note
that some crash bugs were fixed recently.
And there are no -disable-zend-memory-manager or --enable-malloc-mm configure options. To disable
the memory manager (for debugging) you start e.g. apache with same way you do with PHP CLI:
# USE_ZEND_ALLOC=0 /usr/sbin/httpd <your options here>
------------------------------------------------------------------------
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
https://bugs.php.net/bug.php?id=43593
--
Edit this bug report at https://bugs.php.net/bug.php?id=43593&edit=1