Forum: Ruby-core Timeouts in threads cause "ThreadError: deadlock; recursive locking"

Posted by trapni (Christian Parpart) (Guest)
on 2012-11-16 16:46
(Received via mailing list)
Issue #4266 has been updated by trapni (Christian Parpart).


We just ran into this very ugly bug in production, too. We would really 
appreciate a fix in 1.9.4, a pure bugfix release of the 1.9 branch since 
this is a major bug. :)
----------------------------------------
Bug #4266: Timeouts in threads cause "ThreadError: deadlock; recursive 
locking"
https://bugs.ruby-lang.org/issues/4266#change-32969

Author: cjbottaro (Christopher Bottaro)
Status: Assigned
Priority: High
Assignee: ko1 (Koichi Sasada)
Category: core
Target version: 2.0.0
ruby -v: ruby 1.9.2p136 (2010-12-25 revision 30365) 
[x86_64-darwin10.6.0]


=begin
 Run the attached file (or this pastie http://pastie.org/1448542) a few 
times and you'll eventually get:

 ThreadError: deadlock; recursive locking:
 <internal:prelude>:8:in `lock'
 <internal:prelude>:8:in `synchronize'
 bin/deadlock_test.rb:86:in `block (4 levels) in <main>'
 /Users/cjbottaro/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/timeout.rb:57:in 
`timeout'
 bin/deadlock_test.rb:85:in `block (3 levels) in <main>'
 bin/deadlock_test.rb:83:in `times'
 bin/deadlock_test.rb:83:in `block (2 levels) in <main>'

 I've had the script run successfully over 5 times in a row before 
getting the errors, so if it doesn't happen the first few times... keep 
trying.

 The problem doesn't happen in 1.8.7 or Jruby, but does happen in 1.9.1.
=end
Please log in before posting. Registration is free and takes only a minute.
Existing account (Switch to SSL-encrypted connection)
NEW: Do you have a Google/GoogleMail or Yahoo account? No registration required!
Log in with Google account | Log in with Yahoo account
No account? Register here.