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

deadlock when map-ing multiple threads #54

@cldwalker

Description

@cldwalker

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"}

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions