# Sidekiq is consuming too much memory, restarting

**URL:** <https://meta.discourse.org/t/sidekiq-is-consuming-too-much-memory-restarting/48395>\
**Category:** Self-hosting\
**Created:** [9 augustus 2016 om 14:00 UTC](https://meta.discourse.org/t/sidekiq-is-consuming-too-much-memory-restarting/48395 "2016-08-09T14:00:59Z")\
**Posts on this page:** 1\
**Showing post:** 24

<div class="post-metadata">

**Author:** ![schungx](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/schungx/32/70989_2.png) [@schungx](https://meta.discourse.org/u/schungx)\
**Post date:** [11 oktober 2017 om 15:54 UTC](https://meta.discourse.org/t/sidekiq-is-consuming-too-much-memory-restarting/48395/24 "2017-10-11T15:54:13Z")

</div>

It suddenly started appearing to me a couple of days ago.

Before I never saw `Sidekiq is using too much memory` errors in the logs. Now I see them a few times a day.

And today it happened exactly as @pelcami has mentioned: the VM just plainly became unresponsive. SSH didn’t work. No access on HTTP or HTTPS.

The VM is on Azure, so I pulled up the charts, and it showed network activity suddenly dropping down completely to zero (like a cliff) and CPU stuck at around 40% (probably completely using up one core). Restarting the VM solved it.

What I want to say is, it happened so suddenly that it was almost like one minute it was business as usual, normal network traffic, then the next minute it fell off a cliff and dropped to zero. Not gradual at all.

Something is happening to trigger an infinite loop in Sidekiq or something…

---

_[View the full topic](https://meta.discourse.org/t/sidekiq-is-consuming-too-much-memory-restarting/48395)._
