# Locking issues in sidekiq jobs?

**URL:** <https://meta.discourse.org/t/locking-issues-in-sidekiq-jobs/69287>\
**Category:** Product Support\
**Created:** [2017 年9 月 3 日 13:49 UTC](https://meta.discourse.org/t/locking-issues-in-sidekiq-jobs/69287 "2017-09-03T13:49:34Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

作者： ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)\
发布日期： [2019 年1 月 2 日 19:45 UTC](https://meta.discourse.org/t/locking-issues-in-sidekiq-jobs/69287/4 "2019-01-02T19:45:05Z")

</div>

Use rbtrace to get a better back trace

> **[Debugging 100% CPU usage in production Ruby on Rails systems](https://samsaffron.com/archive/2018/01/18/my-production-ruby-on-rails-cpu-is-at-100-now-what)**
>
> Sam's Spot - Sam saffron's web log

---

_[View the full topic](https://meta.discourse.org/t/locking-issues-in-sidekiq-jobs/69287)._