ID: 28177 Comment by: dtan at ftl dot co dot jp Reported By: prof_moriarty at veryfast dot biz Status: Open Bug Type: Apache related Operating System: win xp PHP Version: 5.0.0RC2 New Comment:
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 Previous Comments: ------------------------------------------------------------------------ [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. ------------------------------------------------------------------------ [2004-06-01 07:49:38] dtan at ftl dot co dot jp I am experiencing the same thing. Downloaded the latest snapshot of PHP5 and am currently running it as a module using Apache 1.3.29. Each refresh seems to add about 2-8mbs of memory to the child process. ------------------------------------------------------------------------ [2004-05-16 20:33:37] prof_moriarty at veryfast dot biz Ah. I am now running PHP5RC2 as a module within apache 1.3.x. And it is STILL not releasing RAM when it is done with it. Noting that support for apache 1 is _not_ experimental! Indeed it says this in the install.txt: "Now that version 4.1 introduces a safer sapi module, we recommend that you configure PHP as a module in Apache." So the problem exists with running both versions of Apache with PHP as a module. ------------------------------------------------------------------------ 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
