You can set your own limit in config file.
We set to 128 (try to) only if it's already under 128 : then you can set to 512 if you want in your host : we don't reduce it.

Not a bug

Not a bug : you confirm ?

Not a bug. Memory setting is a server setting - just raise it.

IMHO It is a Bug!
I gave the host a memory_limit of 4G and then I noticed that the limit was still 128M thus the 500 rears its ugly head!

When I increased the config['memory_limit'] the 500 went away!

I just test : no issue : if you set 512Mo in virtual host and 64Mo in LS config : stay 512Mo

But maybe you have an issue on your hoster (i never see a 4G limit ....)

Did you have a look at a phpversion.php file out of limesurvey ?

The 4G (it is allowed) attempt was because of my search to a solution.
I did also a 1024M on the server. But this also got me into a 500.

From the log:
mod_fcgid: stderr: PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 1253376 bytes) in /usr/share/ayh/limesurvey/application/helpers/SurveyRuntimeHelper.php on line 1351

and

mod_fcgid: stderr: PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 130968 bytes) in /usr/share/ayh/limesurvey/framework/web/CUrlManager.php on line 791

This was to me the evidence that the 128M memory_limit was still in place.

BTW It happend during a reload (loadall/reload/scid/...) of a survey!

I already say : my config is 64, but my host is at 512Mo : final memoty_limit : 512

If you have issue : review your host or the mod_fcgid system.

And try toi set 'memory_limit'=>'512', in you config file.

Not a bug : if you really found an issue : send your http://php.net/manual/function.phpinfo.php file (the one provided by LimeSurvey + another one you create on your server)

Actually there is a bug if you don't define the size in your PHP.ini as MB,

Fix committed to master branch: http://bugs.limesurvey.org/plugin.php?page=Source/view&id=18937

Arg .... right ....
php_value memory_limit 1G
don't work ......

Sorry asshank, and thanks for reporting

Fix committed to 2.06lts branch: http://bugs.limesurvey.org/plugin.php?page=Source/view&id=18938

Thank you for not closing this issue.. I did a lot of testing on this one.... and I know PHP and php.ini and limits. (int)G is allowed. (int)M is normal.

Version 2.50 Build 160512 released

Fix committed to 2.06lts branch: http://bugs.limesurvey.org/plugin.php?page=Source/view&id=28087