ID:               36724
 Updated by:       [EMAIL PROTECTED]
 Reported By:      mberg at synacor dot com
-Status:           Open
+Status:           Assigned
 Bug Type:         Apache related
 Operating System: Red Hat Linux 7.2 (ish)
-PHP Version:      4.4.2
+PHP Version:      5.1.3RC3, 4.4.2
 Assigned To:      tony2001


Previous Comments:
------------------------------------------------------------------------

[2006-04-07 20:10:52] mberg at synacor dot com

So have you actually tried this with Apache 1.x?  When you mentioned
not being able to reproduce it earlier you referenced Apache 2.x.

------------------------------------------------------------------------

[2006-03-24 21:33:06] mberg at synacor dot com

Just to be clear, the configurations I produced this under were:

Red Hat Linux 7.2 + Apache 1.3.34 + PHP 4.4.2
CentOS 4.2 + Apache 1.3.34 + PHP 4.4.2
CentOS 4.2 + Apache 1.3.34 + PHP 5.1 (CVS)

This bug will /not/ be reproducable with Apache 2.x.

------------------------------------------------------------------------

[2006-03-16 22:47:08] mberg at synacor dot com

Same behaviour.  Same fix.  Tested on CentOS 4.2 as well.  Same
behaviour.  Same fix.

------------------------------------------------------------------------

[2006-03-15 18:15:10] [EMAIL PROTECTED]

Please try using this CVS snapshot:

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



------------------------------------------------------------------------

[2006-03-15 17:47:47] mberg at synacor dot com

We're always getting a value of 0 logged for %{mod_php_memory_usage}
using stock 4.4.2 with Apache 1.3.34.  It worked as expected with
4.3.11.

Reverting the change introduced in bug #35646 with the following patch
fixed it for us:

--- php-4.4.2.orig/Zend/zend_alloc.c    Sun Jan  1 08:46:49 2006
+++ php-4.4.2/Zend/zend_alloc.c Fri Mar 10 16:59:18 2006
@@ -541 +540,0 @@
-       AG(allocated_memory_peak) = 0;

This presumably breaks Apache 2.x though (_that_ I haven't tested),
which is where the second part of my suggested fix comes in.  This is
just clearing the value in the bit of code in apache2handler that's
analagous to where it was cleared in mod_php4.c.

------------------------------------------------------------------------

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

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

Reply via email to