SOLVED Error memory exhausted gantrylesscompiler.class.php
-
-
- Peter KORTGE
- Hero Rocketeer
- Posts: 359
- Thanks: 3
- Company Owner
-
Hi:
Migrating a working Joomla! v2.5.7 / Gantry v4.1.2 site at iWorld to new template Metropolis v1.0.
However, every now and again the site doesn't load but instead generates error messages as follows:-
Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 39 bytes) in /home/iworld/public_html/cms/libraries/gantry/core/utilities/gantrylesscompiler.class.php on line 757
and
Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 13 bytes) in /home/iworld/public_html/cms/libraries/gantry/core/utilities/gantrylesscompiler.class.php on line 747
Refreshing the screen usually clears the error.
Any ideas as to the problem/solution - the site wasn't generating any memory allocation errors previously. - Last Edit: 12 years 5 months ago by Peter KORTGE.
- Great minds discuss ideas; Average minds discuss events; Small minds discuss people.
-
-
-
- Who?
- Preeminent Rocketeer
- Posts: 25562
- Thanks: 613
- Joomla freelancer
- Try to increase memory_limit parameter in php.ini file
-
The following users have thanked you: Sami Onur Zaim
- Check my services at: Mihha-Vision
-
-
-
- Peter KORTGE
- Hero Rocketeer
- Posts: 359
- Thanks: 3
- Company Owner
-
Igor Mihaljko wrote:
Try to increase memory_limit parameter in php.ini fileHi Igor:
Don't have access to php.ini as this site is on a Shared Host, so I searched the web and found this link 3 Ways to Increase PHP Memory Limit (e.g. increase to 128MB):-
php.ini ... include the following code in .php.ini and then restart apache:-.htaccess ... include the following code in .htaccess:-memory_limit = 128M
Change Memory at Runtime ... include the following code in index.php:-php_value memory_limit 128M ;
ini_set('memory_limit', '128M');
I chose adding the code to Joomla!'s index.php and it seems to be working - but using anything less than 128MB caused the site to not load?
That said, Joomla! [System Information] -> [PHP Information] still shows "memory_limit = 32MB" ?
Why would merely changing a template from Panacea v1.6.5 -> Metropolis v1.0 cause a memory problem? Was it just the "last straw" that broke the site ?
And, is what I've done correct? -
The following users have thanked you: Gerhard Wentzel
- Great minds discuss ideas; Average minds discuss events; Small minds discuss people.
-
-
-
- Who?
- Preeminent Rocketeer
- Posts: 25562
- Thanks: 613
- Joomla freelancer
-
You ask why would merely changing template from Panacea to Metropolis cause a memory problem. I would sat that this is because Metropolis template uses higher server resources for it's presentation and also Metropolis uses css compiler (if needed) to compile less files into the css files. Everything uses memory for that so you need to have more resources for proper working.
You still see 32MB in System information because that page reads values from your php.ini and not from values set "on the fly" - Check my services at: Mihha-Vision
-
-
-
- Peter KORTGE
- Hero Rocketeer
- Posts: 359
- Thanks: 3
- Company Owner
-
Igor Mihaljko wrote:
You ask why would merely changing template from Panacea to Metropolis cause a memory problem. I would sat that this is because Metropolis template uses higher server resources for it's presentation and also Metropolis uses css compiler (if needed) to compile less files into the css files. Everything uses memory for that so you need to have more resources for proper working.Hi Igor:
You still see 32MB in System information because that page reads values from your php.ini and not from values set "on the fly"
Thanks for the reply.
I just wasn't expecting the memory usage to "jump" from 32MB -> 128MB for a template change :frown:
That' a huge jump ... and I suspect it may catch a few hosting people "off guard" if they have servers with 100's of Joomla! sites on them and everyone starts upgrading to newer, more resource intensive Joomla! v3 templates.
Maybe the RT devs should look at including memory_get_peak_usage ??? or something in the next MissionControl template or the Joomla! devs should do something similar - as the [System Tools] -> [System Information] -> [PHP Information] -> [PHP Core] "memory_limit" doesn’t appear to be of much use? -
The following users have thanked you: bvrettski
- Great minds discuss ideas; Average minds discuss events; Small minds discuss people.
-
-
-
- Who?
- Preeminent Rocketeer
- Posts: 25562
- Thanks: 613
- Joomla freelancer
- memory_limit parameter is only for setting up php environment and it is to find out how much memory you actually use. Also, in shared hosting environment, hosting companies usually disallow changing this parameter by hosting users so usually you can't bring server to it's knees
- Check my services at: Mihha-Vision
-
-
-
- Peter KORTGE
- Hero Rocketeer
- Posts: 359
- Thanks: 3
- Company Owner
-
Hi Igor:
I guess we'll all have to "learn to live" with the increased memory requirements for these new "responsive" templates.
I'll mark this thread now as "Solved"
- Great minds discuss ideas; Average minds discuss events; Small minds discuss people.
-
-
-
- Clikz Design
- Rocketeer
- Posts: 86
- Thanks: 0
- "Mistakes are forgi
- I ran into the same problem and was able to solve the problem in WHM by going to "Configure PHP and suEXEC" and making the change from 32 to 128. Thanks for posting the solution.
- Clikz
-
-
-
- Who?
- Preeminent Rocketeer
- Posts: 25562
- Thanks: 613
- Joomla freelancer
- No problem at all
- Check my services at: Mihha-Vision
-
-
-
- roadsider
- Rocketeer
- Posts: 50
- Thanks: 0
- Just to clarify, if you use "ini_set('memory_limit', '128M');" you need to place it in the index.php file in the Template directory, not the root Joomla directory.
-
Time to create page: 0.082 seconds