deadlock when map-ing multiple threads

Open cldwalker opened this issue 13 years ago • 1 comments

As encountered in sferik/twitter#332, the following causes debugger to raise an internal error:

threads = []
[1,2,3].each {|obj| threads << Thread.new { yield obj } }
threads.map(&:value)

I don't have time to look into this. Pull requests welcome to fix this. @gissues:{"order":75,"status":"notstarted"}

Dec 11 '12 03:12 cldwalker

@cldwalker That code raises #<LocalJumpError: no block given (yield)> with both 1.9.3 and 2.0.0. Is the problem that debugger deadlocks instead of rising the same error?

Sep 17 '13 15:09 deivid-rodriguez