Req #43593 [Opn-Fbk]: Impossible to disable Zend Memory Manager in anything other than CLI SAPI

2013-10-01 Thread mike
Edit report at https://bugs.php.net/bug.php?id=43593edit=1

 ID: 43593
 Updated by: m...@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:

$ curl --progress localhost/info.php | grep Memory Manager 

trtd class=eZend Memory Manager /tdtd class=vdisabled /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] j...@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] sni...@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=43593edit=1


#43593 [Opn-Fbk]: Impossible to disable Zend Memory Manager in anything other than CLI SAPI

2008-02-01 Thread jani
 ID:   43593
 Updated by:   [EMAIL PROTECTED]
 Reported By:  phajdan dot jr at gmail dot com
-Status:   Open
+Status:   Feedback
-Bug Type: Unknown/Other Function
+Bug Type: Scripting Engine problem
 Operating System: Linux Gentoo 2007.0
 PHP Version:  5.2CVS-2007-12-14
 New Comment:

How about --disable-malloc-mm ??


Previous Comments:


[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.



[2008-01-29 00:23:03] [EMAIL PROTECTED]

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.





[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] [EMAIL PROTECTED]

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




[2007-12-14 10:38:40] phajdan dot jr at gmail dot com

Wait, I can test everything, but which method should I use (to disable
Zend Memory Manager)? The crashes occur even in 5.3-latest, so please
tell me what should I *exactly* do with this snapshot.



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/43593

-- 
Edit this bug report at http://bugs.php.net/?id=43593edit=1


#43593 [Opn-Fbk]: Impossible to disable Zend Memory Manager in anything other than CLI SAPI

2008-01-28 Thread tony2001
 ID:   43593
 Updated by:   [EMAIL PROTECTED]
 Reported By:  phajdan dot jr at gmail dot com
-Status:   Open
+Status:   Feedback
-Bug Type: PHP options/info functions
+Bug Type: Unknown/Other Function
 Operating System: Linux Gentoo 2007.0
 PHP Version:  5.2CVS-2007-12-14
 New Comment:

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.




Previous Comments:


[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] [EMAIL PROTECTED]

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




[2007-12-14 10:38:40] phajdan dot jr at gmail dot com

Wait, I can test everything, but which method should I use (to disable
Zend Memory Manager)? The crashes occur even in 5.3-latest, so please
tell me what should I *exactly* do with this snapshot.



[2007-12-14 08:43:15] [EMAIL PROTECTED]

Please try using this CVS snapshot:

  http://snaps.php.net/php5.2-latest.tar.gz
 
For Windows (zip):
 
  http://snaps.php.net/win32/php5.2-win32-latest.zip

For Windows (installer):

  http://snaps.php.net/win32/php5.2-win32-installer-latest.msi





[2007-12-14 07:23:21] phajdan dot jr at gmail dot com

Description:

Okay, so generally the PHP website and docs tell me to use following
methods to disable Zend Memory Manager:

Set env var USE_ZEND_ALLOC=0 (works only for CLI)
Compile PHP with --disable-zend-memory-manager or --enable-malloc-mm
(these options do not get recognized; I know the first one has been
removed, and the second one added - but why doesn't it work?)

How do I test whether it works or not? phpinfo has a position called
Zend Memory Manager, which can be either enabled or disabled. If I try
to disable it and it still says enabled I suppose the method doesn't
work.

Last but not least, why would I want to disable the memory manager? I
get horrible crashes with it, I (and not only I) reported it, the bug
got closed as a dupe, but the original bug was also closed with no
feedback etc. And while I believe in fixing the bug itself, it would be
nice to have a workaround.






-- 
Edit this bug report at http://bugs.php.net/?id=43593edit=1


#43593 [Opn-Fbk]: Impossible to disable Zend Memory Manager in anything other than CLI SAPI

2007-12-17 Thread sniper
 ID:   43593
 Updated by:   [EMAIL PROTECTED]
 Reported By:  phajdan dot jr at gmail dot com
-Status:   Open
+Status:   Feedback
 Bug Type: PHP options/info functions
 Operating System: Linux Gentoo 2007.0
 PHP Version:  5.2.5
 New Comment:

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



Previous Comments:


[2007-12-14 10:38:40] phajdan dot jr at gmail dot com

Wait, I can test everything, but which method should I use (to disable
Zend Memory Manager)? The crashes occur even in 5.3-latest, so please
tell me what should I *exactly* do with this snapshot.



[2007-12-14 08:43:15] [EMAIL PROTECTED]

Please try using this CVS snapshot:

  http://snaps.php.net/php5.2-latest.tar.gz
 
For Windows (zip):
 
  http://snaps.php.net/win32/php5.2-win32-latest.zip

For Windows (installer):

  http://snaps.php.net/win32/php5.2-win32-installer-latest.msi





[2007-12-14 07:23:21] phajdan dot jr at gmail dot com

Description:

Okay, so generally the PHP website and docs tell me to use following
methods to disable Zend Memory Manager:

Set env var USE_ZEND_ALLOC=0 (works only for CLI)
Compile PHP with --disable-zend-memory-manager or --enable-malloc-mm
(these options do not get recognized; I know the first one has been
removed, and the second one added - but why doesn't it work?)

How do I test whether it works or not? phpinfo has a position called
Zend Memory Manager, which can be either enabled or disabled. If I try
to disable it and it still says enabled I suppose the method doesn't
work.

Last but not least, why would I want to disable the memory manager? I
get horrible crashes with it, I (and not only I) reported it, the bug
got closed as a dupe, but the original bug was also closed with no
feedback etc. And while I believe in fixing the bug itself, it would be
nice to have a workaround.






-- 
Edit this bug report at http://bugs.php.net/?id=43593edit=1


#43593 [Opn-Fbk]: Impossible to disable Zend Memory Manager in anything other than CLI SAPI

2007-12-14 Thread sniper
 ID:   43593
 Updated by:   [EMAIL PROTECTED]
 Reported By:  phajdan dot jr at gmail dot com
-Status:   Open
+Status:   Feedback
 Bug Type: PHP options/info functions
 Operating System: Linux Gentoo 2007.0
 PHP Version:  5.2.5
 New Comment:

Please try using this CVS snapshot:

  http://snaps.php.net/php5.2-latest.tar.gz
 
For Windows (zip):
 
  http://snaps.php.net/win32/php5.2-win32-latest.zip

For Windows (installer):

  http://snaps.php.net/win32/php5.2-win32-installer-latest.msi




Previous Comments:


[2007-12-14 07:23:21] phajdan dot jr at gmail dot com

Description:

Okay, so generally the PHP website and docs tell me to use following
methods to disable Zend Memory Manager:

Set env var USE_ZEND_ALLOC=0 (works only for CLI)
Compile PHP with --disable-zend-memory-manager or --enable-malloc-mm
(these options do not get recognized; I know the first one has been
removed, and the second one added - but why doesn't it work?)

How do I test whether it works or not? phpinfo has a position called
Zend Memory Manager, which can be either enabled or disabled. If I try
to disable it and it still says enabled I suppose the method doesn't
work.

Last but not least, why would I want to disable the memory manager? I
get horrible crashes with it, I (and not only I) reported it, the bug
got closed as a dupe, but the original bug was also closed with no
feedback etc. And while I believe in fixing the bug itself, it would be
nice to have a workaround.






-- 
Edit this bug report at http://bugs.php.net/?id=43593edit=1