Support » How-To and Troubleshooting » [Resolved] Fatal error: Allowed memory size of 33554432 bytes exhausted

[Resolved] Fatal error: Allowed memory size of 33554432 bytes exhausted

  • What does this mean when I try to access my plugins in the admin?

    Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 7680 bytes) in /home/xyz/public_html/abc/tuv/wp-includes/kses.php(1005) : runtime-created function on line 1

Viewing 15 replies - 1 through 15 (of 23 total)
  • yep thanks… i should of searched first sorry

    excuse me follows but I need to know is IF we increase the memory in wp-settings.php will it consume the PC on hosting service you see my hosting service has a pc usage limit. Thank You

    saaqi – please ask your host HOW they will react to you increasing memory that PHP may consume.

    Note: I deleted the other exact question you asked in 4 other threads.

    go to your webhosting
    edit wp-settings.php [32M to 64M]

    Enjoy Your Rock !!

    You don’t actually need to increase it that much, so try 38M first and move it up slowly multiples of 2 till your error messages disappear, keeping it to a conservative amount may work better overall, especially if you are running more than one WP site on a shared server. Chances are 38M will do just fine, I had the same issue and it worked for me.

    Hello guys,
    i was searching for that and its working now
    Alexthewordpress special thanks 😉
    thanks all 🙂

    edit wp-settings.php [32M to 64M]

    and if you do that your settings will be overwritten with every upgrade
    better to use one of the other solutions

    1. Try adding this line to your wp-config.php file:
    define('WP_MEMORY_LIMIT', '64M');
    2. If you have access to your PHP.ini file, change the line in PHP.ini
    If your line shows 32M try 64M:
    memory_limit = 64M ; Maximum amount of memory a script may consume (64MB)
    3. If you don't have access to PHP.ini try adding this to an .htaccess file:
    php_value memory_limit 64M
    4. Talk to your host.

    I changed my memory limit in wp-settings.php and then it gave me this error:

    Fatal error: Call to undefined function is_admin() in /sitepath/wp-includes/vars.php on line 16

    [Content moderated.]


    I went into php.ini and changed the memory limit to 80M just to go overboard and hope I don’t get errors in WordPress anymore which makes a 30 minute job take 30 days.

    I’ll post up an update if it all goes well and hopefully others can benefit from my trial.

    With cross-browser incompatibility and wordpress errors and people still using IE6, I just don’t know why we can’t just make this all simple with more stable updates (don’t release an update until it is 100% stable [moronic name calling deleted]), upgrade yor browser, use firefox, and get a mac.

    I mean it’s not that difficult [moronic name calling deleted].


    Sir! Please regard your tone and choice of words! Really, If you want help within a community, ranting and raving unnecessarily about the object in question is NO way to get help!

    now, i looked up how to get rid of this error and people advise to re-install wordpress again (WHICH I JUST DID!!)

    Okay, I am not sure what exactly you looked up to try to troubleshoot your problem, but I will see what I can do to respond anyway. First of all, some people may be having problems like this because of a corrupt file, which would be a good reason to reinstall WordPress. But in your case, the error was caused by an edited file. This is probably due to some mismatched syntax, or something of the sort. In short, it probably could have been fixed by reverting to an earlier version of the file (if you made a backup before editing) or finding the problem with your edit.

    man, if I was a php developer I would make an awesome, stable Shopping Cart with great shipping options and then charge $5 to buy it.

    I find it necessary to remind you that the key word in your statement is IF. IF you want to go out and become a PHP dev and write a plugin, that’s great! Really! I’m not being sarcastic. But if you want to become one and contribute to the community by producing a plugin (payed or not, as long as it works well), and then you wouldn’t have to complain.

    WordPress is always bringing out flippn updates that make everyones adrenaline kick in just before you click the upgrade button because more times than not, you get a flippn error message where you have to start you life all over again.

    In computing, errors happen. MAKE BACKUPS. Computers are only as smart as the people directing them, and occasionally there will be slip-ups (whether it’s you, someone at WP, someone at your host, etc.)

    i mean, what the **** is memory allocation anyway ??

    i mean, just use what you need in memory to get the ****ing job done Errorpress.

    Again, please moderate your tone. There are distinct limitations on purpose to prevent errors. If there is a plugin that uses to much memory due to a bug, or a hacker that does it on purpose, the memory limit is there as a safeguard. It also comes in handy when your host knows that there are limitations in place to keep their memory usage within good ranges.

    ok, that seemed to work, and it doesn’t tax my system.

    Problem solved I guess.

    This Worked For Me- Settings then GD Press Tools: Settings
    Then Check Memory allocated by PHP: and I changed my to 120 instead of 64M. (php.ini: memory_limit [120M]) Help that helps someone just like
    moderator Helped Me.

    Thanks Everyone for this information. It resolved memory issues I was having on my blogs.

Viewing 15 replies - 1 through 15 (of 23 total)
  • The topic ‘[Resolved] Fatal error: Allowed memory size of 33554432 bytes exhausted’ is closed to new replies.
Skip to toolbar