-
-
Notifications
You must be signed in to change notification settings - Fork 87
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unhandled Exception does not stop program running #260
Comments
This is probably a bug that can only be fixed by modifying/fixing CRuby. It's probably in the thread exit code path where a scheduler is set, it's ignoring the exception. I'll take a look. |
As a bit of a hack, we can define def scheduler_close
unless $!
self.run
end
ensure
self.close
end and it works as you expect, but I don't like using the implicit |
I'm basically okay with the proposed fix, the chance of |
This should be fixed, please feel free to test it and report back. |
Either this fix or the scheduler closing broke exception handling for me:
After this happens, it hangs. Does not exit. I do not understand what you are trying to do. |
Do you mind giving me a small reproduction? |
I will try. |
For me all problems started with stopping the event loop. There is a trick used by many without OS interrupts. Make a pipe. And select() on the read end of the pipe all the time. And if you want to interrupt, then you write a byte to the write end of the pipe. Maybe it is completely unrelated, but i hope this may help you. |
It is all good. |
It's all good, let me know if you run into any other issues. |
Unhandled Exception does not stop program running:
(does work when uncommenting Fiber.schedule do)
The text was updated successfully, but these errors were encountered: