Title: memory issues
Last modified: May 21, 2026

---

# memory issues

 *  Resolved [nosilver4u](https://wordpress.org/support/users/nosilver4u/)
 * (@nosilver4u)
 * [6 days, 5 hours ago](https://wordpress.org/support/topic/memory-issues-16/)
 * Hi,
 * I was working on something yesterday on a site with QM installed, and kept getting
   502 errors from my site. After a lot of investigation with my web host, it was
   determined that it was a memory error, and I believe we’ve narrowed it down to
   QM and Types (Toolset). My suspicion is that because Types is throwing a bunch
   of PHP deprecations, QM is using up too much memory in storing the debugging 
   info and exhausts the available memory.
 * Otherwise, the site has a 512MB memory limit, and normally uses around 50-60MB(
   per QM’s stats). But when attempting to submit settings changes, activate plugins,
   purge caches, any sort of “action” request, then I get the memory issues.
 * I believe there are a couple other plugins that have PHP deprecations also (running
   on PHP 8.4), so perhaps it is a cumulative effect, but I’m not certain.
 * Any ideas on how to narrow this down further, or make it so QM doesn’t suck up
   all the memory?
 * Thanks!

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

 *  Plugin Author [John Blackbourn](https://wordpress.org/support/users/johnbillion/)
 * (@johnbillion)
 * WordPress Core Developer
 * [6 days, 5 hours ago](https://wordpress.org/support/topic/memory-issues-16/#post-18914970)
 * Yeah a large number of PHP errors can eat up memory due to the size of the stack
   trace that’s collected alongside each one. Query Monitor version 4 reduces that
   memory usage considerably, but it’s still potentially unbounded.
 * The nuclear option is to disable error handling in QM completely:
 *     ```wp-block-code
       define( 'QM_DISABLE_ERROR_HANDLER', true );
       ```
   
 * Not ideal, but it’ll allow you to use all the other panels in QM.
 * Short of changing the way QM transiently stores the data that it collects, there’s
   not really anything I can do about this. Any attempt to put a limit on the number
   of queries or errors that QM collects immediately makes it less useful when you
   inevitably need to see that information.
 * [QM also allows you to hide errors from certain plugins or themes](https://querymonitor.com/help/silencing-errors/),
   but this doesn’t stop the data being collected, it just prevents the admin toolbar
   from showing a coloured notification. Perhaps I need to introduce a new option
   for completely bypassing the collection of errors from certain plugins and themes.
 *  Thread Starter [nosilver4u](https://wordpress.org/support/users/nosilver4u/)
 * (@nosilver4u)
 * [6 days, 1 hour ago](https://wordpress.org/support/topic/memory-issues-16/#post-18915173)
 * Hmm, while that isn’t ideal, it might help narrow things down. Besides error 
   reporting, it’s entirely possible the issues are related to db queries or something
   else that is happening on those requests.
 * I’ll try it out and see if the issue is indeed from the error handler, or somewhere
   else. Thanks!

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

You must be [logged in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fwordpress.org%2Fsupport%2Ftopic%2Fmemory-issues-16%2F%3Foutput_format%3Dmd&locale=en_US)
to reply to this topic.

 * ![](https://ps.w.org/query-monitor/assets/icon.svg?rev=2994095)
 * [Query Monitor](https://wordpress.org/plugins/query-monitor/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/query-monitor/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/query-monitor/)
 * [Active Topics](https://wordpress.org/support/plugin/query-monitor/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/query-monitor/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/query-monitor/reviews/)

 * 2 replies
 * 2 participants
 * Last reply from: [nosilver4u](https://wordpress.org/support/users/nosilver4u/)
 * Last activity: [6 days, 1 hour ago](https://wordpress.org/support/topic/memory-issues-16/#post-18915173)
 * Status: resolved