#40701 [Opn->Fbk]: Memory allocation error
ID: 40701 Updated by: [EMAIL PROTECTED] Reported By: michaeldaly at magma dot ca -Status: Open +Status: Feedback Bug Type: Unknown/Other Function Operating System: Win XP Pro PHP Version: 5.2.2 New Comment: We still have no idea on how to reproduce it. Previous Comments: [2007-04-10 18:06:36] michaeldaly at magma dot ca Two snaps have been applied since the last suggestion with no chnage - the problem still occurs. [2007-04-05 01:00:00] php-bugs at lists dot php dot net No feedback was provided for this bug for over a week, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open". [2007-03-28 08:41:53] [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 [2007-03-27 23:07:11] priyadi at priyadi dot net I think I found the culprit. In my case it is my ulimits. my previous ulimits were (taken from 'ulimit -a'): core file size (blocks, -c) 0 data seg size (kbytes, -d) 20480 file size (blocks, -f) unlimited max locked memory (kbytes, -l) 4 max memory size (kbytes, -m) unlimited open files (-n) 1024 pipe size (512 bytes, -p) 8 stack size (kbytes, -s) 10240 cpu time (seconds, -t) 60 max user processes (-u) 20 virtual memory (kbytes, -v) 20480 now they are: core file size (blocks, -c) 0 data seg size (kbytes, -d) 204800 file size (blocks, -f) unlimited max locked memory (kbytes, -l) 4 max memory size (kbytes, -m) unlimited open files (-n) 1024 pipe size (512 bytes, -p) 8 stack size (kbytes, -s) 10240 cpu time (seconds, -t) 600 max user processes (-u) 200 virtual memory (kbytes, -v) 204800 so, my case is probably not related to this bug, sorry. [2007-03-27 22:35:54] priyadi at priyadi dot net this occurs to me too with PHP 5.2.1 and mediawiki 1.9.3. in my case, the error message stays constant: "Fatal error: Out of memory (allocated 5242880) (tried to allocate 1245184 bytes) in */web/languages/messages/MessagesEn.php on line 2106. this is on RHEL 3. memory_limit is set to 128M and PHP is using CGI API, so I don't think this problem is related to apache. this works in my development machine though (gentoo, same PHP version running as apache 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/40701 -- Edit this bug report at http://bugs.php.net/?id=40701&edit=1
#40701 [Opn->Fbk]: Memory allocation error
ID: 40701 Updated by: [EMAIL PROTECTED] Reported By: michaeldaly at magma dot ca -Status: Open +Status: Feedback Bug Type: Unknown/Other Function Operating System: Win XP Pro PHP Version: 5.2.2 New Comment: 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. Previous Comments: [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 [2007-03-07 16:04:57] michaeldaly at magma dot ca > It _does_ report 8Mb - "PHP Fatal error: Out of memory (allocated > 8388608) (tried to allocate 393216 bytes)". It also reports from 786KB to 9.2MB, so it appears that if the problem is a limit set externally, that limit is floating dynamically. > Yes, please search for "memory_limit" in your scripts,.htacess > and httpd.conf. I searched for "memory" in the entire Apache directory tree and found nothing that resembles a limit. I looked through httpd.conf and httpd_vhosts.conf visually and can find nothing else that looks like a memory restriction. The only limit I can find is in PHP.ini. [2007-03-07 09:13:06] [EMAIL PROTECTED] >PHP does _not_ report 8MB - it reports 512MB as per the php.ini setting. It _does_ report 8Mb - "PHP Fatal error: Out of memory (allocated 8388608) (tried to allocate 393216 bytes)". >This is reported in phpinfo.php. memory_limit can be changed per-virtualhost, per-directory and per-script. Therefore phpinfo() might show you 512Mb, but the real script might use different value. >Is there a way for me to capture some kind of debug information >that can help you? Yes, please search for "memory_limit" in your scripts,.htacess and httpd.conf. [2007-03-06 20:54:33] michaeldaly at magma dot ca Is there a way for me to capture some kind of debug information that can help you? I downloaded the debug files along with the latest snap and they were just PDB files and I don't know what to do with them. 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
#40701 [Opn->Fbk]: Memory allocation error
ID: 40701 Updated by: [EMAIL PROTECTED] Reported By: michaeldaly at magma dot ca -Status: Open +Status: Feedback Bug Type: Unknown/Other Function Operating System: Win XP Pro PHP Version: 5.2.2 New Comment: >PHP does _not_ report 8MB - it reports 512MB as per the php.ini setting. It _does_ report 8Mb - "PHP Fatal error: Out of memory (allocated 8388608) (tried to allocate 393216 bytes)". >This is reported in phpinfo.php. memory_limit can be changed per-virtualhost, per-directory and per-script. Therefore phpinfo() might show you 512Mb, but the real script might use different value. >Is there a way for me to capture some kind of debug information >that can help you? Yes, please search for "memory_limit" in your scripts,.htacess and httpd.conf. Previous Comments: [2007-03-06 20:54:33] michaeldaly at magma dot ca Is there a way for me to capture some kind of debug information that can help you? I downloaded the debug files along with the latest snap and they were just PDB files and I don't know what to do with them. [2007-03-06 18:10:37] [EMAIL PROTECTED] Cannot reproduce anything like that. [2007-03-06 18:02:56] michaeldaly at magma dot ca I can find no other mechanism for setting a memory limit. PHP does _not_ report 8MB - it reports 512MB as per the php.ini setting. This is reported in phpinfo.php. This allocation error is occurring at many different allocation levels. For example, the following occurred yesterday. The first column is the allocated amount, the second is the amount attempted and the third is the number of times it occurred. Allocated AddFreq 1048576 6144 1 1835008 98304 2 2359296 98304 2 2883584 24576 3 3407872 24576 2 3670016 24576 2 4456448 6144 1 5242880393216 1 5505024 98304 1 5767168 1572864 3 5767168 98304 1 6029312393216 1 6291456 1572864 2 6291456 98304 1 6553600 1572864 1 6553600 24576 1 6553600393216 8 6815744393216 4 7077888 1572864 11 7340032 1572864 5 7602176 1572864 1 7602176393216 1 786432 24576 4 786432 6144 3 9175040 1572864 2 All these values are well below the 512MB limit. [2007-03-05 10:02:55] [EMAIL PROTECTED] Make sure you didn't set the memory limit in any other way (windows registry, httpd.conf, htaccess etc.). If PHP says your limit is set to 8Mb, I see no reason why I shouldn't trust PHP. [2007-03-04 20:21:23] michaeldaly at magma dot ca Additional thought - may be unrelated. On my old server (Apache 1.6.3, PHP 5.0) I never saw this problem but had another, possibly related. There was a frequent bug that I fixed with Win32DisableAcceptEx in httpd.conf. This then introduced a memory allocation bug in Apache. Apparently, that situation was relatively common on Windows machines with not a lot of RAM - mine was 512MB. With current server, I have 2GB Ram and the Apache allocation bug hasn't shown up. However, now PHP has allocation errors. Is it possible one was "hiding" the other? Is it possible the two situations are related? I only mention this in the hope it might twig one of you PHP wizards. 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
#40701 [Opn->Fbk]: Memory allocation error
ID: 40701 Updated by: [EMAIL PROTECTED] Reported By: michaeldaly at magma dot ca -Status: Open +Status: Feedback Bug Type: Unknown/Other Function Operating System: Win XP Pro PHP Version: 5.2.1 New Comment: Cannot reproduce anything like that. Previous Comments: [2007-03-06 18:02:56] michaeldaly at magma dot ca I can find no other mechanism for setting a memory limit. PHP does _not_ report 8MB - it reports 512MB as per the php.ini setting. This is reported in phpinfo.php. This allocation error is occurring at many different allocation levels. For example, the following occurred yesterday. The first column is the allocated amount, the second is the amount attempted and the third is the number of times it occurred. Allocated AddFreq 1048576 6144 1 1835008 98304 2 2359296 98304 2 2883584 24576 3 3407872 24576 2 3670016 24576 2 4456448 6144 1 5242880393216 1 5505024 98304 1 5767168 1572864 3 5767168 98304 1 6029312393216 1 6291456 1572864 2 6291456 98304 1 6553600 1572864 1 6553600 24576 1 6553600393216 8 6815744393216 4 7077888 1572864 11 7340032 1572864 5 7602176 1572864 1 7602176393216 1 786432 24576 4 786432 6144 3 9175040 1572864 2 All these values are well below the 512MB limit. [2007-03-05 10:02:55] [EMAIL PROTECTED] Make sure you didn't set the memory limit in any other way (windows registry, httpd.conf, htaccess etc.). If PHP says your limit is set to 8Mb, I see no reason why I shouldn't trust PHP. [2007-03-04 20:21:23] michaeldaly at magma dot ca Additional thought - may be unrelated. On my old server (Apache 1.6.3, PHP 5.0) I never saw this problem but had another, possibly related. There was a frequent bug that I fixed with Win32DisableAcceptEx in httpd.conf. This then introduced a memory allocation bug in Apache. Apparently, that situation was relatively common on Windows machines with not a lot of RAM - mine was 512MB. With current server, I have 2GB Ram and the Apache allocation bug hasn't shown up. However, now PHP has allocation errors. Is it possible one was "hiding" the other? Is it possible the two situations are related? I only mention this in the hope it might twig one of you PHP wizards. [2007-03-04 17:40:36] michaeldaly at magma dot ca phpinfo shows memory_limit 512M. BTW this coincides with an Apache error of: Parent: child process exited with status 3221225477 -- Restarting. And -access violation (hex of 3221225477 is 0xC005) according to a post on a web site I found. This error with php apparently has a long history and comes and goes by mixing and matching different versions of Apache and PHP. I don't know if this adds any useful information, but it sounds like one of those nasty problems that is hard to debug and fix. [2007-03-04 17:23:43] [EMAIL PROTECTED] What memory limit value phpinfo() show? 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
#40701 [Opn->Fbk]: Memory allocation error
ID: 40701 Updated by: [EMAIL PROTECTED] Reported By: michaeldaly at magma dot ca -Status: Open +Status: Feedback -Bug Type: Reproducible crash +Bug Type: Unknown/Other Function Operating System: Win XP Pro PHP Version: 5.2.1 New Comment: Make sure you didn't set the memory limit in any other way (windows registry, httpd.conf, htaccess etc.). If PHP says your limit is set to 8Mb, I see no reason why I shouldn't trust PHP. Previous Comments: [2007-03-04 20:21:23] michaeldaly at magma dot ca Additional thought - may be unrelated. On my old server (Apache 1.6.3, PHP 5.0) I never saw this problem but had another, possibly related. There was a frequent bug that I fixed with Win32DisableAcceptEx in httpd.conf. This then introduced a memory allocation bug in Apache. Apparently, that situation was relatively common on Windows machines with not a lot of RAM - mine was 512MB. With current server, I have 2GB Ram and the Apache allocation bug hasn't shown up. However, now PHP has allocation errors. Is it possible one was "hiding" the other? Is it possible the two situations are related? I only mention this in the hope it might twig one of you PHP wizards. [2007-03-04 17:40:36] michaeldaly at magma dot ca phpinfo shows memory_limit 512M. BTW this coincides with an Apache error of: Parent: child process exited with status 3221225477 -- Restarting. And -access violation (hex of 3221225477 is 0xC005) according to a post on a web site I found. This error with php apparently has a long history and comes and goes by mixing and matching different versions of Apache and PHP. I don't know if this adds any useful information, but it sounds like one of those nasty problems that is hard to debug and fix. [2007-03-04 17:23:43] [EMAIL PROTECTED] What memory limit value phpinfo() show? [2007-03-04 01:31:59] michaeldaly at magma dot ca Further note on memory allocations: here are the three latest failures and the programs in which they occured; the top one being the most recent and the bottom the oldest. (allocated 1835008) (tried to allocate 98304 bytes) Parser.php (allocated 2883584) (tried to allocate 24576 bytes) Language.php (allocated 7340032) (tried to allocate 1572864 bytes) MessagesEn.php [2007-03-03 17:18:56] michaeldaly at magma dot ca PHP responds to other parameters in the PHP.ini file (e.g. display_errors = Off/On) so it is being found and used. As I stated in my report "The amount of memory allocated or attempted to allocate varies.". I wasn't clear - I have seen this bug occur with allocated reported at just over 1MB to just over 8MB and more often at lower levels - the specific, most recent, error message I showed is one of the larger values I've seen. Please reconsider this bug. 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
#40701 [Opn->Fbk]: Memory allocation error
ID: 40701 Updated by: [EMAIL PROTECTED] Reported By: michaeldaly at magma dot ca -Status: Open +Status: Feedback Bug Type: Reproducible crash Operating System: Win XP Pro PHP Version: 5.2.1 New Comment: What memory limit value phpinfo() show? Previous Comments: [2007-03-04 01:31:59] michaeldaly at magma dot ca Further note on memory allocations: here are the three latest failures and the programs in which they occured; the top one being the most recent and the bottom the oldest. (allocated 1835008) (tried to allocate 98304 bytes) Parser.php (allocated 2883584) (tried to allocate 24576 bytes) Language.php (allocated 7340032) (tried to allocate 1572864 bytes) MessagesEn.php [2007-03-03 17:18:56] michaeldaly at magma dot ca PHP responds to other parameters in the PHP.ini file (e.g. display_errors = Off/On) so it is being found and used. As I stated in my report "The amount of memory allocated or attempted to allocate varies.". I wasn't clear - I have seen this bug occur with allocated reported at just over 1MB to just over 8MB and more often at lower levels - the specific, most recent, error message I showed is one of the larger values I've seen. Please reconsider this bug. [2007-03-03 15:50:08] [EMAIL PROTECTED] Based on the error it would seem that the limit is 8 megs not 512 as your config suggests. I suspect your configuration file is being ignored. [2007-03-03 02:37:12] michaeldaly at magma dot ca Description: PHP 5.2.2-dev (2007-02-28-1530 snap) Apache 2.2.4 Mediawiki 1.9.2 MySQL 5.0.27. XP Pro SP2+all current updates. After editing about 15-20 pages in my Wiki, PHP eventually generates an error: PHP Fatal error: Out of memory (allocated 8388608) (tried to allocate 393216 bytes) The error occurs in several php programs, though MessagesEn.php is the most common. The amount of memory allocated or attempted to allocate varies. PHP.ini currently has: max_execution_time = 30 max_input_time = 60 memory_limit = 512M Computer has 2GB RAM and is not near its limit in paging etc. It sounds similar to a bug that was reported as fixed in 5.2.0. -- Edit this bug report at http://bugs.php.net/?id=40701&edit=1
