Title: Memory Hogging
Last modified: May 17, 2017

---

# Memory Hogging

 *  Resolved [garikaib](https://wordpress.org/support/users/garikaib/)
 * (@garikaib)
 * [9 years ago](https://wordpress.org/support/topic/memory-hogging-2/)
 * Just tried both the Hookr and WP Inspect plugins because of the promised magical
   ability to show all executed hooks. Both started chomping on memory like crazy
   resulting in my 4GB RAM being eaten in minutes. And with just 30 active connections
   I cannot blame this on traffic

Viewing 1 replies (of 1 total)

 *  Plugin Author [explodybits](https://wordpress.org/support/users/explodybits/)
 * (@explodybits)
 * [9 years ago](https://wordpress.org/support/topic/memory-hogging-2/#post-9142260)
 * Garikai,
 * As I mentioned in my comment on the original article via WP Tavern, the only 
   recourse you have is to adjust WP Inspect’s settings to achieve the desired memory
   usage:
 * -Disable plugins that you are not debugging
    -Enable only actions or filters -
   Toggle contexts, headers, middle, footer & off-screen -Disable backtrace
 * Also, I do not recommend running this in a production environment, as this is
   a debug tool and does require in-memory operations to run.

Viewing 1 replies (of 1 total)

The topic ‘Memory Hogging’ is closed to new replies.

 * ![](https://s.w.org/plugins/geopattern-icon/wp-inspect_3eb8fc.svg)
 * [WP Inspect](https://wordpress.org/plugins/wp-inspect/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/wp-inspect/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/wp-inspect/)
 * [Active Topics](https://wordpress.org/support/plugin/wp-inspect/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/wp-inspect/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/wp-inspect/reviews/)

 * 1 reply
 * 1 participant
 * Last reply from: [garikaib](https://wordpress.org/support/users/garikaib/)
 * Last activity: [9 years ago](https://wordpress.org/support/topic/memory-hogging-2/)
 * Status: resolved