Project

General

Profile

Actions

Bug #15360

closed

"ThreadError: deadlock; recursive locking" error when recursive lock shouldn't be possible

Added by brockspratlen (Brock Spratlen) over 5 years ago. Updated over 4 years ago.

Status:
Closed
Assignee:
-
Target version:
-
ruby -v:
ruby 2.5.3p105 (2018-10-18 revision 65156) [x86_64-darwin17]
[ruby-core:90170]

Description

I think I've discovered a Ruby bug, possibly introduced in 2.5.

I've attached a reproduction script; running it on Ruby 2.5.0+ (including previews of 2.6.0) seems to always produce a flood of printed ThreadError: deadlock; recursive locking exceptions, even though the reproduction code doesn't appear to do any recursive locking.

Running the same script on Ruby 2.4.5 doesn't produce any ThreadError: deadlock; recursive locking exceptions. I've run the script several times on Ruby 2.4.5, I simply can't reproduce the raising of ThreadError: deadlock; recursive locking with this script on 2.4.5.

Curiously, removing the puts e.class on line 24 causes the bug to go away: ThreadError: deadlock; recursive locking never gets raised regardless of which Ruby version I'm running. Given this oddity, I can't help but think the issue is something around writing to stdout. This change in particular looks suspect: https://bugs.ruby-lang.org/issues/9323

Thank you!
Brock


Files

deadlock_test.rb (556 Bytes) deadlock_test.rb Run with "ruby deadlock_test.rb" brockspratlen (Brock Spratlen), 11/29/2018 06:09 PM

Related issues 2 (0 open2 closed)

Related to Ruby master - Bug #15508: Mutex recursive lock error when combined with Thread#raiseClosedActions
Related to Ruby master - Bug #15645: It is possible to escape `Mutex#synchronize` without releasing the mutexClosedActions
Actions

Also available in: Atom PDF

Like0
Like0Like0Like0Like0Like0Like0Like0Like0Like0Like0