post-page

WordPress and the Fatal Memory Error

14
responses
by
 
on
August 29th, 2010
in
WordPress, WordPress Troubleshooting
heading
heading
heading
14
Responses

 

Comments

  1. Yohan Perera (5 comments.) says:

    I had this problem for a long time and had a hard time until my host fixed the problem. As you have said none of the solutions given in this post worked, because they were subject to override by my server’s configuration…

  2. Big Dave Zatz (2 comments.) says:

    If this occurs out of the blue, there are also other things to check… When I started getting it, I was pretty confused because my Twitter widget in the sidebar had never produced that error before. Turns out, my site had been hacked and there was some malicious code injected into the sidebar. So the memory limitation actually prevented my site/db from being hacked further. So maybe a lower limit is actually reasonable… as protection and to help you weed out poorly programmed plugins.

    • Marko Paulus (1 comments.) says:

      I’m curious…what version of WordPress are you using? It should be quite hack-proof by now.

      • Big Dave Zatz (2 comments.) says:

        I was running the current version at the time. Unfortunately, my hosting provider seemed to have some insecurities between shared accounts which made me vulnerable from the inside.

    • James Huff (62 comments.) says:

      Thanks for reminding me about that! I’ve made a tiny update to the post about potential plugin or theme issues.

      I don’t know how it slipped my mind. Perhaps I’m having a fatal memory error. . . :)

  3. Computer Lover (1 comments.) says:

    Thanks for the article; this is a fairly common issue and whilst I knew overriding the php.ini file, I wasn’t aware this was possible to do via the .htaccess file.

    Also you make a good point about switching hosts if they won’t help you out after the other options have been tried. One of my first hosts were a major overseller and in the end I had to move because none of my dynamic sites were working properly.

  4. Doctor Thomas says:

    The fatal memory error in WordPress can be a sheep in wolf’s clothing. Depending on the plug-ins activated at the time one attempts to up-load, up-date or otherwise change their administrative controls, the noted error can be understood as a warning sign of a conflict with installed plug-ins and attempted changes/additions. The problem is not always your host’s low server memory allocation.

    I have experienced the memory error on numerous occasions on numerous sites. Simple deactivation of currently installed plug-ins and then performing the same process that erred out has worked every time. Subsequent re-activation of the plug-ins has been unproblematic. A number of useful plug-ins that otherwise perform wonderfully have triggered the error message. [Naming those plug-ins here would serve no useful purpose; some readers might assume inherent errors in the plug-ins and that would be misleading and uselessly detrimental.]

    Note: The plug-in conflict is by no means the only vehicle to arrive at the error message. This has been my experience only.

  5. Jimmy (3 comments.) says:

    Has this problem but dealt with by wordpress? I’ve never experienced it. I regularly get a page that says it cannot connect with the server. Probably should change hosting provider for that one.

    • James Huff (9 comments.) says:

      Well, it’s not a problem that WordPress can deal with. More than likely, the problem is caused by either an overzealous plugin or theme, or severe resource restrictions from your hosting provider.

      Either way, it sounds like you have a great hosting provider since you’ve never seen this before, but then again the connection failures make me think otherwise.



Trackbacks/Pingbacks

  1. […] de nuestro sistema. Para intentar reservar más memoria disponible en nuestro sistema la gente de WeblogToolsCollection.com publica un artículo recopilatorio de soluciones al famoso “Fatal error: Allowed memory size of 33554432 bytes exhausted.” […]

  2. […] de nuestro sistema. Para intentar reservar más memoria disponible en nuestro sistema la gente de WeblogToolsCollection.com publica un artículo recopilatorio de soluciones al famoso “Fatal error: Allowed memory size of 33554432 bytes […]

  3. […] Screen of Death. If you’re seeing “Fatal error: Allowed memory size,” consult WordPress and the Fatal Memory Error. If you’re seeing an internal server error or error 500, consult WordPress and the Internal […]

  4. […] WordPress and the Fatal Memory Error […]

Obviously Powered by WordPress. © 2003-2013

page counter
css.php