#40701 [Com]: Interesting observation

2007-03-27 Thread priyadi at priyadi dot net
 ID:   40701
 Comment by:   priyadi at priyadi dot net
 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:

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.


Previous Comments:


[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).



[2007-03-25 20:19:42] michaeldaly at magma dot ca

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.



[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 )
(tried to allocate  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.



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 [Com]: Interesting observation

2007-03-27 Thread priyadi at priyadi dot net
 ID:   40701
 Comment by:   priyadi at priyadi dot net
 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:

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).


Previous Comments:


[2007-03-25 20:19:42] michaeldaly at magma dot ca

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.



[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 )
(tried to allocate  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.



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