Issue #9432 has been updated by Aaron Stone.


Note: Sidekiq does not appear to be using eventmachine, which has a similar bug at #9132. Any ideas on what is going on here? I can reproduce the bug from all releases of Ruby 2.0.0pxxx including 2.0.0p598.

----------------------------------------
Backport #9432:  ThreadError [ Attempt to unlock a mutex which is locked by another thread ]
https://bugs.ruby-lang.org/issues/9432#change-50387

* Author: rajesh shanmugam
* Status: Open
* Priority: Normal
* Assignee: 
----------------------------------------
I use ruby-2.0.0-p247. I seem to get this issue frequently in threaded environment. (Sidekiq) 

I am not very sure if it a ruby thread issue as such or something I am doing wrong. If there is any more details you need I would be happy to provide you.

Operating system: Ubuntu

Trace

```
/home/ubuntu/.rvm/rubies/ruby-2.0.0-p247/lib/ruby/2.0.0/thread.rb:188:in `synchronize'
/home/ubuntu/.rvm/rubies/ruby-2.0.0-p247/lib/ruby/2.0.0/thread.rb:188:in `block in pop'
/home/ubuntu/.rvm/rubies/ruby-2.0.0-p247/lib/ruby/2.0.0/thread.rb:187:in `handle_interrupt'
/home/ubuntu/.rvm/rubies/ruby-2.0.0-p247/lib/ruby/2.0.0/thread.rb:187:in `pop'
```

Regards
Rajesh



-- 
https://bugs.ruby-lang.org/