Gabriel, you were right! It was a problem with jailshell / cpanel. We fixed it
by disabling fork bomb protection.
For anybody else with this problem, look here...
http://www.mickgenie.com/blog/jailed-shell-memory-issue/
Date: Wed, 23 Mar 2011 10:43:57
To: symfony-users@googlegroups.com
Reply-To: symfony-users@googlegroups.com
Subject: [symfony-users] Re: cli memory problem...
Hi Gabriel. Thanks! Following ur advice, I used a script to test memory usage
that I found here...
http://magazine.joomla.org/issues/Issue
Hi Gabriel. Thanks! Following ur advice, I used a script to test memory usage
that I found here...
http://magazine.joomla.org/issues/Issue-Dec-2010/item/295-Are-you-getting-your-fair-share-of-PHP-memory?tmpl=componentprint=1
And you were right! Through the web, the script happily gets up to
My suspicion is that the limitation is not related to PHP or Apche in any
way, it's probably some setting on a system level that affects all running
processes.
That is why I said that you should try also with a compiled C program this
test to verify that the limitation affects all processes.
Thanks Gabriel. Since my last email, i tried to run php with the -n flag (to
use no php.ini). With this flag, my script can get up to 80mb, which is the
limit set by the the bash stack (i think).
So it appears that it is something in or loaded by the php.ini.
Looking at the output from...
Just a wild guess, maybe there is something on the hosting provider side
that still limits process memory usage, so it may only look like it's not
limited for PHP script.
My suggestion is to test this assumption, create a simple PHP scripts that
consumes memory and see how much memory it can
You can also try explicitly setting the memory limit in your project
configuration via:
ini_set(memory_limit, 60M); or whichever is appropriate.
Expecially long-running tasks can be hogs.
Daniel
On Mar 22, 8:35 am, Jonathan Franks jonat...@ifranks.com wrote:
Hi, I know this issue has been
