• After upgrading to the latest Query Monitor (3.12.1) and WPML (4.6.3) version I am seeing these errors in the WordPress log:

    [30-Mar-2023 09:39:27 UTC] PHP Fatal error:  Allowed memory size of 536870912 bytes exhausted (tried to allocate 20480 bytes) in /xyz/wp-content/plugins/query-monitor/classes/Backtrace.php on line 528
    
    [30-Mar-2023 09:39:27 UTC] PHP Fatal error:  Allowed memory size of 536870912 bytes exhausted (tried to allocate 20480 bytes) in /xyz/wp-content/plugins/query-monitor/classes/Backtrace.php on line 528
    
    [30-Mar-2023 09:39:27 UTC] PHP Fatal error:  Allowed memory size of 536870912 bytes exhausted (tried to allocate 20480 bytes) in /xyz/wp-content/plugins/query-monitor/classes/Util.php on line 599
    
    [30-Mar-2023 09:39:32 UTC] PHP Fatal error:  Allowed memory size of 536870912 bytes exhausted (tried to allocate 20480 bytes) in /xyz/wp-content/plugins/query-monitor/classes/Backtrace.php on line 528
    
    [30-Mar-2023 09:40:51 UTC] PHP Fatal error:  Allowed memory size of 536870912 bytes exhausted (tried to allocate 20480 bytes) in /xyz/wp-content/plugins/query-monitor/classes/Backtrace.php on line 528

    The Query Monitor menu is empty in this case. It is 100% reproducible on the prod and staging environments.

    Looks like a possible endless loop in the backtrace code.

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

    (@johnbillion)

    WordPress Core Developer

    Thanks for the report. This is most likely because of the high number of database queries that WPML performs. The sheer amount of data that QM collects can exhaust the memory usage if the number of queries is high and the memory limit on the server is low.

    There’s not much that can be done about this at the moment other than trying to increase the memory limit on your server or deactivating other plugins that you’re not using.

    The next release of QM will actually use less memory for its data collection as it’s a problem I’ve been working on recently. No ETA just yet though.

    Thread Starter Christoph Bratschi

    (@cbratschi)

    Thanks, I increased the limits to 768 MB and it works so far. Perhaps this was related to the ACFML plugin which updated translations. This was only executed once.

    Looking forward to the next release. Thanks a lot for this great plugin.

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