-
Notifications
You must be signed in to change notification settings - Fork 630
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
Segfault from EM.run after EM::Connection#unbind raises exception #765
Comments
Thank you! I've got your repro script and PR #766 and now I'm cooking on a fix! |
I assume this will be fixed in the 1.2.3 release? |
Please try the new EventMachine 1.2.3 release, it should resolve this crash! |
The original repro case still segfaults in eventmachine 1.2.3. It seems to be 100% reproable, re-open or new issue?
|
Yes, sadly the 1.2.3 release just moved the same crash to a different line. I am working on a followup fix. |
@sodabrew Thanks for your work on this! Any progress with the followup? |
We are experiencing the same segfault. It happens often, but not always. If I understood the discussion here correctly, this has to do with an exception being raised at a time when eventmachine does not correctly deal with it. As it would help me with debugging the issue on our side: Is there a way to find out what exception is being raised that then triggers the problem in eventmachine? While we wait for a fix in this gem, maybe that will help us work around the issue on our side... |
I don't know if this issue is specific to exceptions raised from Or use For the PoC case, removing the
The |
@SpComb Thanks for the tip! However, nothing of value was printed out right before the crash (some other warnings and exceptions earlier in the code, but not related to the crash). |
I experienced a segfault similar to #758 and #761 when trying to write rspecs for a
faye/websocket
client, using anEM.run { ... }
pattern similar totests/test_unbind_reason.rb
.The following minimal repro crashes with a segfault when run with
CRASH_EM=1
:ruby bin/em-test
CRASH_EM=1 ruby bin/em-test
The text was updated successfully, but these errors were encountered: