Fatal Error – Memory size exhausted
Searching will usually help.
thanks, I did a search, but didn’t hit the right combination of terms I guess.
Now take back your slap on the wrist, K?
Ok Jeremy… I searched the forum you suggested and nobody has a fix. So the next time you flame somebody for bad search terms, you might just shut up unless you have a link to a fix.
Forums are for help. Not flames.
My first reply was not in any way a flame, I was just pointing out the fact that searches usually turn up the answer, I then proceeded to give you a link that would help.
But you’ll need to contact your host, very rarely are end users able to change any php settings. You can try this in your .htaccess file
php_value memory_limit 16M
And just for your information the link that was given in the second post in this topic spelled it out very clearly, oh it also happens to be the first in the search results as well.
Bluehost changed the damn PHP engine from PHP 4 to PHP 5 which means that just about every WordPress blog out on Bluehost is going to break. The WordPress Database Backup plugin will no longer work with PHP 5 so I moved it to a temporary folder on the server in order to deactivate it. I also set the PHP memory limit to 20M in two PHP files (cache.php and pluggable.php) which got you back up and running for now.
i have also the same error while installing at localhost:
Fatal error: Allowed memory size of 8388608 bytes exhausted (tried to allocate 98304 bytes) in C:\Program Files\VertrigoServ\www\projects\blogs\wp-admin\includes\schema.php on line 37.
Any body can help me?
Edit your php.ini file and look for this
memory_limit = 8M
Change it to this
memory_limit = 32M
This is maybe a little off topic, but I just ran into a similar PHP memory exhausted error, I recently upgraded my server to PHP5, and I’ve already upped my PHP memory limit twice, from the default 8M to 10M then 12M, to deal with problems in other apps. Now it seems it should go up to 32M…
My question is based on what I’ve gathered, that simply upping the PHP mem limit is not too sound a fix, that these memory errors generally result from poor coding (memory leaks?). How accurate and relevant is this? Is it not good to just up the limit?
I get the same problem with the “upload” part of the admin, it’s apparently the miniature creation that causes problem, because the image itself is uploaded, and NO, I cannot augment memory being on a shared hosting. Did someone at least try to find another solution than “read the other threads” (that I did) and “augment the memory” (that I can not) ?
hey.. The same problem with me… I just changed the WAMP server version and it worked…
I think this is due to aome PHP version… try getting the latest PHP version and this problem might vanish..
All the best..
If the problem is with the thumbnail creation or lack of it then it’s most likely that the host doesn’t have GD support compiled into php. GD is a graphics extension for php that allows resizing and all that.
As far as doing something about the memory limit if you can’t increase it then try disabling all plugins that you don’t need.
Nope, GD2 is compiled, according to the phpinfo. As for the plugins, having no plugin or just the “Get recent comments” does not change anything. I am sending a mail to the hosting support to see what they can do for the version of PHP. Thanks both for the ideas.
Where do you find the php.ini? I also have to change the momemry size. Please assist.
The php.ini file is not always available on every host. If you are hosted with Bluehost, you can click on the ‘PHPConfig’ option within the cpanel and choose to install the master php.ini file. It will install as php.ini.default, so you’ll have to rename it to php.ini. Bluehost is pretty smart about the settings, so it should automatically have the memory_limit = 32M But you can always change it to anything else if needs be. If you are not with Bluehost, you may want to check with your host to see if they allow the usage of a php.ini file.
- The topic ‘Fatal Error – Memory size exhausted’ is closed to new replies.