Thread

I get this error every now and then.
Fatal error: Allowed memory size of 37748736 bytes exhausted (tried to allocate 252507 bytes) in /smi/web/site.com/system/expressionengine/libraries/Template.php on line 1315

I have not found a solution to the problem .. I wonder if i can get some help in here..

Greating /Tomas

Hi, Tomas.

Have you seen: EEWiki:// HowTo Determine Memory Limits

-and-

EEWiki:// HowTo Override Memory Limitations

It sounds like you should increase the value of memory_limit to 64M.

Does that help?

Hi, thanks Sue;
I forgot to mention: we have looked up the memory_limit and it is set to 128 MB (both local and master); but we are on a shared host, so maybe we do not get all that memory to ourself, we will check this with our provider.

Is there a way to see how much memory EE is using? The error occurs in the Templates.php file, so are we right to assume that it is some template/s that are taking up too much memory? The error states that the memory limit of ~33 MB is exceeded, but as mentioned above the php_info says that we have 128 MB - this is confusing to us.

Hi Tomas,

Please let us know what you find out from your host on this. It could well be that it has something to do with being on a shared server yes.

With regards to seeing how much memory ExpressionEngine is using you can go to :

Admin > System Administration > Output and Debugging

and turn on the option that says Display Output Profiler?.

This should then give you some (hopefully) helpful information.

Hope that helps a little.

Thanks,

Mark

Hey!
Sorry for delay. We found the error: its was the memory_limit setting in a plugin; we had missed to double check the configuration of that plugin.

Moreover, our host told us that the memory_limit value from php_info represents the memory allocated to each PHP-process; that is each script run has that memory, so it is not divided among users or any such.

The interesting thing we learnt here was that even though the ‘memory limit exceeded’-message appeared in a certain line of code (in the core in this case), it can still originate from an other script (a plugin in this case).

Thank you

Glad you were able to figure out what the problem was. Don’t hesitate to post again as needed.