• Resolved Nico Marcuz

    (@nick7766)


    Hi There!

    Today we get the following fatal errors in our php errorlog.

    thnx for helping

    Nick

    ==========
    [25-Oct-2022 12:51:34 UTC] PHP Fatal error: Allowed memory size of 536870912 bytes exhausted (tried to allocate 20480 bytes) in /kunden/customer_id/webseiten/hello-world.net/wordpress/wp-content/plugins/query-monitor/classes/Backtrace.php on line 511
    [25-Oct-2022 12:51:38 UTC] PHP Fatal error: Allowed memory size of 536870912 bytes exhausted (tried to allocate 20480 bytes) in /kunden/customer_id/webseiten/hello-world.net/wordpress/wp-content/plugins/query-monitor/classes/Backtrace.php on line 444
    [25-Oct-2022 12:51:40 UTC] PHP Fatal error: Allowed memory size of 536870912 bytes exhausted (tried to allocate 20480 bytes) in /kunden/customer_id/webseiten/hello-world.net/wordpress/wp-content/plugins/query-monitor/classes/Backtrace.php on line 511

    The page I need help with: [log in to see the link]

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author John Blackbourn

    (@johnbillion)

    WordPress Core Developer

    This just unfortunately means there’s too much data for QM to collect on your site and it’s running out of memory. This can be caused by an exceptionally high number of database queries, translations, hooks, HTTP API requests, etc. It really depends.

    Unfortunately there’s nothing that QM can do about this at the moment. Your best bet, as always, is to try to reduce the number of queries and other operations that your site does.

    Thread Starter Nico Marcuz

    (@nick7766)

    Thnx John for your reply.

    Do I understand correctly that this is not an error/problem on our side, but that QueryMonitor has just received too much data to process?

    This means that if QueryMonitor had not been active in this case, we would not have had an error message in the PHP ErrorLog. Right?

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘PHP Fatal error’ is closed to new replies.