Skip to content
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

each is broken on Linux #9

Closed
boazsegev opened this issue Dec 18, 2016 · 1 comment
Closed

each is broken on Linux #9

boazsegev opened this issue Dec 18, 2016 · 1 comment

Comments

@boazsegev
Copy link
Owner

For some reason, each is broken on Linux, while working flawlessly on macOS.

Tests have yielded no apparent reason so far, though it might have something to do with closing connections (and might not).

The error received is "segfault" for address 0x00000....04

Attempting to reproduce with C code (no Ruby) did not yield any errors nor segmentation faults.

The issue is being researched, but is (of yet) unresolved.

@boazsegev
Copy link
Owner Author

Seems to have been an issue where a protocol lock was "unlocked" while on_open was running, allowing each to call on a Websocket object even before the initialization of it's core data was complete.

Resolved in version 0.2.5

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

No branches or pull requests

1 participant