• Jesse

    (@drummingpariah)


    I have to admit, I’m at a bit of a loss on this one. I recently resized my web host to 1024mb RAM to handle the recent increase in traffic, and when the server came back up, I was greeted with a friendly 404 page. I turned debugging on, and got a little more information.

    Fatal error: Allowed memory size of 33554432 bytes exhausted
    (tried to allocate 64 bytes) in
    /home/webuser/public_html/wp-includes/wp-db.php on line 1402

    However, after going through what I already knew (adjust wp-config.php’s memory allocation as well as the php.ini file), I was still receiving the same error.

    $cat wp-config.php | grep define\(\'WP_MEMORY
    define('WP_MEMORY_LIMIT', '512M');

    (for the corresponding directory’s php.ini)

    cat php.ini | grep memory_limit
    memory_limit = 512M

    I can’t see any reason to be running out of memory, especially with such a tiny request. This is a multisite installation, and when visiting other sites with more plugins installed, I get even more fun errors.

    Notice: wp_register_script was called incorrectly.
    Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or init hooks.
    Please see Debugging in WordPress for more information. (This message was added in version 3.3.) in /home/webuser/public_html/wp-includes/functions.php on line 3587
    Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 491520 bytes) in
    /home/webuser/public_html/wp-content/themes/thejournal/functions/admin-shortcodes.php
    on line 1603

    which basically says the same thing, but for different function calls. None of my .htaccess files include any kind of memory limitation, so I’m not sure where else to look. Has anyone else had a similar memory-limitation error with 3.3?

    Apache is running fine, and hosting other sites without issue (sugarcrm, django sites, and perlcgi). It seems like this is a very wordpress-specific cause of this error.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Have you tried switching to a default theme and seeing if that rectifies the error? Have you tried to restart the server after making the PHP adjustment?

    Have you set php_value post_max_size xxxM to a higher number in php.ini? If it’s still set low around 30, that could be the cause of your problem.

    Thread Starter Jesse

    (@drummingpariah)

    Sorry, I should have specified that that’s how I got the first error. The barebones, no-plugins, twenty-twelve theme produces the error when trying to access the database, it seems.

    I temporarily set post_max_size to 128M, but I can’t imagine that even a value of 16M would cause an issue for an empty site with one post and no fancy php being run.

    I’m at a bit of a loss still, so any other advice, files to check, settings to confirm, or suggestions (no matter how obvious they may seem) would be greatly appreciated.

    Thread Starter Jesse

    (@drummingpariah)

    Any other ideas from anyone?

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Memory size exhausted’ is closed to new replies.