Support Forum

Fatal error: allowed memory size

DE DeadMan
DeadMan
Member

I have various podcasts that I post on my site and link them to the forums for discussion and whatnot. Multiple times now I have gotten an error message that looks like this

Fatal error: Allowed memory size of 100663296 bytes exhausted (tried to allocate 76550145 bytes) in /problem-with-post-edit-buttonome/dead2010/domains/deathsdoorprods.com/public_html/wp-includes/class-http.php on line 1106

and like that one every time the amount of data the forum attempts to allocate is always smaller than the allowed memory size. any ideas how to keep this from happening?

5 Answers

New Answer

MP Mr Papa
Mr Papa
Member

have you tried increasing your php memory? the message simply says what the latest code tried to allocate – it does not say what has already been allocated…

WA warnerbob18
warnerbob18
Member

I am also going through same problem, Is this serious error or this is a general error..?

YS Yellow Swordfish
Yellow Swordfish
Member

This is not, as such, an ‘error’. It simply means that you do not have enough php memory available to run everything you are trying to run on your site. So you need to increase the allocation your host has set up for you – if they will let you.

You could firstly try this do it yourself method – http://wiki.simple-press.com/installation/troubleshooting/increase-php-memory/

If that doesn’t work then you will have to ask your hosting company for more.

Or reduce the amount of code being run. Start by ensuring that any plugins you do not really want are deactivated – and I am really talking about WP here not SP. Each one adds code and uses up available memory.

DE DeadMan
DeadMan
Member

but would increasing the php memory help when the amount of data trying to be allocated is smaller than the allowed memory?

YS Yellow Swordfish
Yellow Swordfish
Member

Read the message again and Steve’s reply in post 2. It said it had exhausted the memory allocation and had tried to allocate some more. In the process of trying to allocate the extra memory needed it hit the maximum allowed – so failed to do so.