Skip to content
This repository has been archived by the owner on Nov 15, 2021. It is now read-only.

deadlock when map-ing multiple threads #54

Open
cldwalker opened this issue Dec 11, 2012 · 1 comment
Open

deadlock when map-ing multiple threads #54

cldwalker opened this issue Dec 11, 2012 · 1 comment
Labels

Comments

@cldwalker
Copy link
Owner

As encountered in sferik/twitter-ruby#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"}

@deivid-rodriguez
Copy link

@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?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants