Bug #16110

Doesn't detect deadlock on Ruby 2.4 and 2.5 on Windows

Added by josh.cheek (Josh Cheek) about 1 year ago. Updated 5 months ago.

Target version:
ruby -v:
ruby 2.5.5p157 (2019-03-15 revision 67260) [i386-mingw32]


The following code is detected as a deadlock, except in Ruby 2.4 and 2.5 on Windows:

ruby -r thread -ve ' { }.join'

You can see it run in this code:

And it gets stuck in AppVeyor's CI because it doesn't realize it's deadlocked:

Updated by MSP-Greg (Greg L) about 1 year ago

Is this specific to 32 bit builds of 2.4 & 2.5? I think 64 bit builds all function as expected...

Updated by jeremyevans0 (Jeremy Evans) 5 months ago

  • Status changed from Open to Closed

I tested 32-bit Windows builds of Ruby 2.6 and 1.9.3 and the deadlock is detected (those are the only 32-bit versions I have installed in my Windows environment). I tested on 64-bit builds of Ruby 2.0-2.7, and deadlock is detected in all cases. Maybe this problem is limited to 32-bit Windows builds of Ruby 2.4 and 2.5. However, as Ruby 2.4 is out of support and Ruby 2.5 has already moved into the security maintenance phase, this can be closed. Please update to Ruby 2.6 or 2.7.

Also available in: Atom PDF