ID: 40701 User updated by: michaeldaly at magma dot ca -Summary: no change Reported By: michaeldaly at magma dot ca Status: Open Bug Type: Unknown/Other Function Operating System: Win XP Pro PHP Version: 5.2.2 New Comment:
While testing a new php program, I inadvertently coded an infinite loop. While running it, the thing failed at over 400MB with an allocation error. This shows the config is capable of using lots of memory and the repeated failures at 0.7MB to 9MB seem anomalous. Previous Comments: ------------------------------------------------------------------------ [2007-03-21 15:55:02] edwin at aucs dot org I think I am getting the same problem with php5.2-win32-200703210430.zip I am getting "PHP Fatal error: Out of memory (allocated <random size>) (tried to allocate <random size> bytes)" after the server started for a while. May be this is something related to memory leakage with mysql, as in Listing 7 of http://www.ibm.com/developerworks/opensource/library/os-php-v521/ ? ------------------------------------------------------------------------ [2007-03-16 16:49:25] michaeldaly at magma dot ca That version has no effect. However, I'm not so sure it's any different than the version I started with - Feb 28 build that included the early Feb memory fix. ------------------------------------------------------------------------ [2007-03-14 11:31:32] [EMAIL PROTECTED] Please try using this CVS snapshot: http://snaps.php.net/php5.2-latest.tar.gz For Windows: http://snaps.php.net/win32/php5.2-win32-latest.zip A fix for memory manager was applied to CVS recently, it might solve this issue. ------------------------------------------------------------------------ [2007-03-13 04:55:55] michaeldaly at magma dot ca With memory_limit = -1 there is no change. ------------------------------------------------------------------------ [2007-03-12 03:40:34] [EMAIL PROTECTED] Just out of the curiousity: what happens when you disable memory limit altogether? memory_limit=-1 ------------------------------------------------------------------------ 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/40701 -- Edit this bug report at http://bugs.php.net/?id=40701&edit=1
