ID:               28177
 Updated by:       [EMAIL PROTECTED]
 Reported By:      prof_moriarty at veryfast dot biz
-Status:           Open
+Status:           Closed
 Bug Type:         Apache related
 Operating System: win xp
 PHP Version:      5.0.0RC2
 New Comment:

Ok, closing then.


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

[2004-06-12 18:42:05] prof_moriarty at veryfast dot biz

Bug seems to be fixed in PHP5-RC3, for both Apache 1.x and 2.x.
I believe this bug can now be closed.

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

[2004-06-04 09:39:33] dtan at ftl dot co dot jp

Bug 27758 has seemingly been squashed.  I have taken the latest CVS
snapshot and the problem seems to be resolved.  Seems like memory is
actually being freed ;)

dtan

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

[2004-06-02 14:01:39] prof_moriarty at veryfast dot biz

Not a windows issue:
from:
http://bugs.php.net/bug.php?id=27758

"Apache 2.0.48 on Gentoo"

Seems someone has bug squishing to do. :)

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

[2004-06-02 03:09:28] dtan at ftl dot co dot jp

Yes I noticed that too.  I ran a script which basically checks for a
single variable and otherwise just spits out html.  It still increased
by about 100k.   Running phppgadmin increases the process mem by a few
MB.  I am running windows 2000 and apache 1.3.31 and the lastest
snapshot.  Seems this might be a windows dev/config issue:

  http://bugs.php.net/bug.php?id=27758

dtan

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

[2004-06-01 08:29:48] prof_moriarty at veryfast dot biz

The memory taken per refresh is seems to be entirely dependent on the
script you're running.
Goes up by a few k when i run small scripts, but when i run major
processing scripts, it uses megs (as it normally would), but neglects
to clear them when done.

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

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

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

Reply via email to