Title: CPU Resource Heavy?
Last modified: August 22, 2016

---

# CPU Resource Heavy?

 *  [Debi](https://wordpress.org/support/users/burntrose/)
 * (@burntrose)
 * [11 years, 9 months ago](https://wordpress.org/support/topic/cpu-resource-heavy/)
 * Not sure if it’s a misconfiguration. Never tried with another version of WP –
   It spikes the resources and ultimately crashes the site. – deactivated plugin
   and site is fine. I really like this plugin and would like to use it. Any ideas?
   Using Customizr theme (latest version). It was also displaying the images off
   centre.(to the right).
 * [https://wordpress.org/plugins/fullscreen-galleria/](https://wordpress.org/plugins/fullscreen-galleria/)

Viewing 1 replies (of 1 total)

 *  Plugin Author [pdamsten](https://wordpress.org/support/users/pdamsten/)
 * (@pdamsten)
 * [11 years, 8 months ago](https://wordpress.org/support/topic/cpu-resource-heavy/#post-5271099)
 * I haven’t noticed any resource eating on my site ([http://torturedmind.org/](http://torturedmind.org/)).
   Might be some conflict with other plugins but it’s hard to say.

Viewing 1 replies (of 1 total)

The topic ‘CPU Resource Heavy?’ is closed to new replies.

 * ![](https://ps.w.org/fullscreen-galleria/assets/icon-256x256.png?rev=1003688)
 * [Fullscreen Galleria](https://wordpress.org/plugins/fullscreen-galleria/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/fullscreen-galleria/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/fullscreen-galleria/)
 * [Active Topics](https://wordpress.org/support/plugin/fullscreen-galleria/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/fullscreen-galleria/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/fullscreen-galleria/reviews/)

## Tags

 * [crashing](https://wordpress.org/support/topic-tag/crashing/)

 * 1 reply
 * 2 participants
 * Last reply from: [pdamsten](https://wordpress.org/support/users/pdamsten/)
 * Last activity: [11 years, 8 months ago](https://wordpress.org/support/topic/cpu-resource-heavy/#post-5271099)
 * Status: not resolved