• Eventual WP critical error page “this website has a critical error” pops up when navigating around the site at random pages. When we see the page, sometimes a refresh will bring the page back.

    Checking logs (edited sensitive data):

    [XX-XX-2024 15:XX:02 UTC] PHP Fatal error: Uncaught Error: Xdebug has detected a possible infinite loop, and aborted your script with a stack depth of ‘512’ frames in /XX/XX/XX/XX/plugin.php:989 Stack trace:

    #6 /xx/xx/xx/xx/plugins/w3-total-cache/DbCache_WpdbNew.php(246): wpdb->prepare(‘SELECT option_v…’, ‘auth_key’)

    More info might be needed for this, but essentially, it’s the only plugin mentioned in this stack trace and if you deacivate W3, no more critical errors occur.

    All other themes and plugins are up to date on the site, as well as WordPress core.

    Can anyone help?

Viewing 9 replies - 1 through 9 (of 9 total)
  • Plugin Contributor Marko Vasiljevic

    (@vmarko)

    Hello @igorshiota

    Thank you for reaching out and I am happy to help!
    Can you please share when you started to experience this issue, meaning if you have changed the configuration within the plugin or server?
    Can you also please share which caching method you are using for DB caching?

    Thanks!

    Thread Starter cucurutcho

    (@igorshiota)

    Hi Marko, thanks for your reply. We have noticed the issue a few days after we installed the plugin. I could send you the export of the settings we have if you like? Let me know the best way to send you that.

    W3 is the only caching method we use. Let me know if you need any other info.

    Plugin Contributor Marko Vasiljevic

    (@vmarko)

    Hello @igorshiota

    Thank you for your feedback.
    In the Performance>General settings, Database caching section, what is the caching method selected for Database caching?

    Thanks!

    Thread Starter cucurutcho

    (@igorshiota)

    It’s this:

    Database Cache: Enable

    Database Cache method Disk

    Plugin Contributor Marko Vasiljevic

    (@vmarko)

    Hello @igorshiota

    Thank you for your feedback.

     The disk-based caching is not that efficient. In other words, if you are on a shared hosting, it’s recommended not to use database caching.

    Moreover, using disk-database caching (on shared hosting) can make your site slower. This is so because getting data from the database can be faster than getting cached data from the disk
    This being said, if you do not have an option for memory-based caching like Redis or Memcached, please disable DB caching, save all settings, and purge the cache.

    Let me know if this helps!

    Thanks!

    Thread Starter cucurutcho

    (@igorshiota)

    Hi Marko, we are doing some memory management in our server, so I’m not sure about direct db queries (which could cause out of mem for us)

    We do run a dedicated server (not shared) and we have nvme ssd, so we shouldn’t have problems with disk as they’re super fast. So I’m not sure issue is related to that? Could we investigate further?

    Plugin Contributor Marko Vasiljevic

    (@vmarko)

    Hello @igorshiota

    Thank you for your feedback.
    Generally speaking it’s not a good idea to use Database caching with Disk based caching solution.

    Can you please run the setup guide wizard and let me know what is the recommended setting for DB caching?

    Also do you have an option to use Redis or Memcached?
    Thanks!

    Thread Starter cucurutcho

    (@igorshiota)

    Hi Marko, we have this:

    Storage Engine / Time (ms)

    None / 1044.79

    Disk (selected) / 1.07(-99.90%)

    Memcached / 2.13 (-99.80%)

    The other options are there but they say Unavailable.

    Plugin Contributor Marko Vasiljevic

    (@vmarko)

    Hello @igorshiota

    Please switch to memcached and let me know if this helps!

    Thanks!

Viewing 9 replies - 1 through 9 (of 9 total)

The topic ‘Fatal Error – Infinite Loop’ is closed to new replies.