The lack of the at_exit handler causes hard deadlocks #200
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
We should add a new method for installing the |
|
This is only a problem on MRI 1.9.3, 2.0.0-p0 does not have this issue. |
|
I started a discussion somewhat related to this at https://groups.google.com/d/msg/celluloid-ruby/Rd2AurcPNpo/xejk2OT3zwEJ Mainly questioning whether we should support "no default actors". |
halorgium
added a commit
that referenced
this pull request
Apr 19, 2013
The lack of the at_exit handler causes hard deadlocks
|
+1 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
If you run this: https://gist.github.com/halorgium/14465667d26e4b053180
You will get a deadlock.
This is definitely an issue with
TaskFibers only asTaskThreadbehaves correctly.We either need to add the
at_exithandler back or get to the root cause.