[Plugin: W3 Total Cache] Allowed memory size of [xyz] bytes exhausted

  • entropid

    (@entropid)


    9 years, 1 month ago

    I recently installed W3 Total Cache on a WordPress instance. My PHP log is filled with this (repeating over and over, my log is 33 MB big after a couple of days):

    [22-Mar-2015 15:53:29 UTC] PHP Fatal error:  Allowed memory size of 134217728 bytes exhausted (tried to allocate 8529719 bytes) in /home/wordpress-blog/www/wp-includes/wp-db.php on line 1034
[22-Mar-2015 15:53:29 UTC] PHP Stack trace:
[22-Mar-2015 15:53:29 UTC] PHP   1. {main}() /home/wordpress-blog/www/index.php:0
[22-Mar-2015 15:53:29 UTC] PHP   2. require() /home/wordpress-blog/www/index.php:17
[22-Mar-2015 15:53:29 UTC] PHP   3. require_once() /home/wordpress-blog/www/wp-blog-header.php:12
[22-Mar-2015 15:53:29 UTC] PHP   4. require_once() /home/wordpress-blog/www/wp-load.php:29
[22-Mar-2015 15:53:29 UTC] PHP   5. require_once() /home/wordpress-blog/www/wp-config.php:108
[22-Mar-2015 15:53:29 UTC] PHP   6. do_action() /home/wordpress-blog/www/wp-settings.php:353
[22-Mar-2015 15:53:29 UTC] PHP   7. call_user_func_array:{/home/wordpress-blog/www/wp-includes/plugin.php:496}() /home/wordpress-blog/www/wp-includes/plugin.php:496
[22-Mar-2015 15:53:29 UTC] PHP   8. dsq_request_handler() /home/wordpress-blog/www/wp-includes/plugin.php:496
[22-Mar-2015 15:53:29 UTC] PHP   9. wp_schedule_single_event() /home/wordpress-blog/www/wp-content/plugins/disqus-comment-system/disqus.php:514
[22-Mar-2015 15:53:29 UTC] PHP  10. _set_cron_array() /home/wordpress-blog/www/wp-includes/cron.php:48
[22-Mar-2015 15:53:29 UTC] PHP  11. update_option() /home/wordpress-blog/www/wp-includes/cron.php:440
[22-Mar-2015 15:53:29 UTC] PHP  12. W3_Db->update() /home/wordpress-blog/www/wp-includes/option.php:287
[22-Mar-2015 15:53:29 UTC] PHP  13. W3_DbCache->update() /home/wordpress-blog/www/wp-content/plugins/w3-total-cache/lib/W3/Db.php:109
[22-Mar-2015 15:53:29 UTC] PHP  14. W3_DbCallUnderlying->update() /home/wordpress-blog/www/wp-content/plugins/w3-total-cache/lib/W3/DbCache.php:222
[22-Mar-2015 15:53:29 UTC] PHP  15. W3_Db->update() /home/wordpress-blog/www/wp-content/plugins/w3-total-cache/lib/W3/Db.php:485
[22-Mar-2015 15:53:29 UTC] PHP  16. W3_DbProcessor->update() /home/wordpress-blog/www/wp-content/plugins/w3-total-cache/lib/W3/Db.php:109
[22-Mar-2015 15:53:29 UTC] PHP  17. W3_Db->default_update() /home/wordpress-blog/www/wp-content/plugins/w3-total-cache/lib/W3/Db.php:323
[22-Mar-2015 15:53:29 UTC] PHP  18. wpdb->update() /home/wordpress-blog/www/wp-content/plugins/w3-total-cache/lib/W3/Db.php:193
[22-Mar-2015 15:53:29 UTC] PHP  19. wpdb->prepare() /home/wordpress-blog/www/wp-includes/wp-db.php:1799
[22-Mar-2015 15:53:29 UTC] PHP  20. array_walk() /home/wordpress-blog/www/wp-includes/wp-db.php:1170
[22-Mar-2015 15:53:29 UTC] PHP  21. wpdb->escape_by_ref() /home/wordpress-blog/www/wp-includes/wp-db.php:1170
[22-Mar-2015 15:53:29 UTC] PHP  22. wpdb->_real_escape() /home/wordpress-blog/www/wp-includes/wp-db.php:1114
[22-Mar-2015 15:53:29 UTC] PHP  23. mysqli_real_escape_string() /home/wordpress-blog/www/wp-includes/wp-db.php:1034

    and this

    [22-Mar-2015 16:00:53 UTC] PHP Fatal error:  Allowed memory size of 134217728 bytes exhausted (tried to allocate 3618844 bytes) in /home/wordpress-blog/www/wp-includes/functions.php on line 377
[22-Mar-2015 16:00:53 UTC] PHP Stack trace:
[22-Mar-2015 16:00:53 UTC] PHP   1. {main}() /home/wordpress-blog/www/wp-admin/post.php:0
[22-Mar-2015 16:00:53 UTC] PHP   2. edit_post() /home/wordpress-blog/www/wp-admin/post.php:229
[22-Mar-2015 16:00:53 UTC] PHP   3. wp_update_post() /home/wordpress-blog/www/wp-admin/includes/post.php:321
[22-Mar-2015 16:00:53 UTC] PHP   4. wp_insert_post() /home/wordpress-blog/www/wp-includes/post.php:3572
[22-Mar-2015 16:00:53 UTC] PHP   5. wp_transition_post_status() /home/wordpress-blog/www/wp-includes/post.php:3426
[22-Mar-2015 16:00:53 UTC] PHP   6. do_action() /home/wordpress-blog/www/wp-includes/post.php:3957
[22-Mar-2015 16:00:53 UTC] PHP   7. call_user_func_array:{/home/wordpress-blog/www/wp-includes/plugin.php:496}() /home/wordpress-blog/www/wp-includes/plugin.php:496
[22-Mar-2015 16:00:53 UTC] PHP   8. _future_post_hook() /home/wordpress-blog/www/wp-includes/plugin.php:496
[22-Mar-2015 16:00:53 UTC] PHP   9. wp_schedule_single_event() /home/wordpress-blog/www/wp-includes/post.php:5657
[22-Mar-2015 16:00:53 UTC] PHP  10. _set_cron_array() /home/wordpress-blog/www/wp-includes/cron.php:48
[22-Mar-2015 16:00:53 UTC] PHP  11. update_option() /home/wordpress-blog/www/wp-includes/cron.php:440
[22-Mar-2015 16:00:53 UTC] PHP  12. maybe_serialize() /home/wordpress-blog/www/wp-includes/option.php:274
[22-Mar-2015 16:00:53 UTC] PHP  13. serialize() /home/wordpress-blog/www/wp-includes/functions.php:377

    I have read on other support topics that this could be solved by increasing the amount of memory available to PHP through WordPress configuration (WP_MEMORY_LIMIT). However, if PHP is already taking up 134 MB of memory, I think that something might be wrong?

    My W3 Total Cache installation is configured to use disk: enhanced for page cache, memcached for database and object cache. Minify is off.

  • The topic ‘[Plugin: W3 Total Cache] Allowed memory size of [xyz] bytes exhausted’ is closed to new replies.