#41713 [Asn]: Persistent memory consumption since 5.2
ID: 41713 User updated by: mplomer at gmx dot de Reported By: mplomer at gmx dot de Status: Assigned Bug Type: Performance problem Operating System: win32 only PHP Version: 5.2CVS-2007-07-12 Assigned To: dmitry New Comment: Yes, seems this is the same problem. You could try to reproduce this with the 4-line test script from the comment from [30 Jun 10:19am UTC] and the Reproduce procedure from the initial bug report on your machine. But Jani could already reproduce the bug and it is now assigned to Dmitry, so we will wait for his comments ;-) Previous Comments: [2007-07-16 23:23:32] stephen dot johnston at guildlaunch dot com We are seeing a similar problem in 5.2.3 with Apache 2.0.59 and 4g of RAM. After a few hours of running with more than 70 threads per child in Apache PHP will start throwing errors saying out of memory with seemingly random memory sizes. It seems to happen in our environment once Apache's memory usage reaches around 1gig, but that is not always the case. Our site is growing fast and we need to be able to up Apache threads without recycling Apache every 2 hours. Unfortunately, the PHP community in general seems to respond to error reports relating to this with increase your memory limit. This is *not* a memory limit issue. I would be more than willing to work with you all to provide debug info, but we cannot reproduce this in our test environement with load testing and I don't want to mess around with our production environment without some specific direction on how to correctly profile this issue. [2007-07-14 21:15:15] [EMAIL PROTECTED] And I can reproduce this too on Windows, using latest snapshot available. [2007-07-14 09:15:28] [EMAIL PROTECTED] Dmitry, please check this out. [2007-07-11 08:43:55] mplomer at gmx dot de I tested with PHP 5.2.0 now, and I can reproduce the described behaviour from [30 Jun 10:19am UTC] too. Only when I am testing with PHP 5.1.6, I can't reproduce it. But I agree with you, that this points at the new memory management on win32. [2007-07-10 23:39:09] spamtrap at psychoticwolf dot net I see this with PHP 5.2.1 - 5.2.3 (mod_php5 with Apache 2.0.59 and 2.2.4 on WinXP and Win2003). I did some regression testing and it seems to have started between 5.2.0 and 5.2.1 which points at the new memory management on win32. Memload was normal under 5.2.0. After awhile, Apache consumes as previously reported, 300-600mb (usually around 330mb + 6-700mb virtual), and, curiously, PHP thows a Fatal Error that its exceeded its memory limit for that script, even though it hasn't, as the script doesn't use more than about 300k. (Only seen this last part once, so far, so that might be a fluke.) 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/41713 -- Edit this bug report at http://bugs.php.net/?id=41713edit=1
#41713 [Asn]: Persistent memory consumption since 5.2
ID: 41713 Updated by: [EMAIL PROTECTED] Reported By: mplomer at gmx dot de Status: Assigned Bug Type: Performance problem Operating System: win32 only -PHP Version: 5.2CVS-2007-06-26 +PHP Version: 5.2CVS-2007-07-12 Assigned To: dmitry New Comment: And I can reproduce this too on Windows, using latest snapshot available. Previous Comments: [2007-07-14 09:15:28] [EMAIL PROTECTED] Dmitry, please check this out. [2007-07-11 08:43:55] mplomer at gmx dot de I tested with PHP 5.2.0 now, and I can reproduce the described behaviour from [30 Jun 10:19am UTC] too. Only when I am testing with PHP 5.1.6, I can't reproduce it. But I agree with you, that this points at the new memory management on win32. [2007-07-10 23:39:09] spamtrap at psychoticwolf dot net I see this with PHP 5.2.1 - 5.2.3 (mod_php5 with Apache 2.0.59 and 2.2.4 on WinXP and Win2003). I did some regression testing and it seems to have started between 5.2.0 and 5.2.1 which points at the new memory management on win32. Memload was normal under 5.2.0. After awhile, Apache consumes as previously reported, 300-600mb (usually around 330mb + 6-700mb virtual), and, curiously, PHP thows a Fatal Error that its exceeded its memory limit for that script, even though it hasn't, as the script doesn't use more than about 300k. (Only seen this last part once, so far, so that might be a fluke.) [2007-07-09 13:48:22] mplomer at gmx dot de Does somebody have any ideas to track this down? Are there any PHP core developers with a windows-test-environment? Aren't there any PHP developers who have the problem, that Apache/PHP eats up all RAM after some hours of developing and testing bigger PHP-projects? [2007-06-30 11:32:59] mplomer at gmx dot de Another developer tested this on his own machine now, with the same Apache/PHP environment, and could affirm this behavior. The memory usage values are respectively 0,1-0,3 MB different, but the principle is the same. So the behavior seems not to be system dependent. 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/41713 -- Edit this bug report at http://bugs.php.net/?id=41713edit=1
