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

Jump to bottom

Crash if closing ReactiveSocket immediately after opening it #308

Closed
lexs opened this issue Feb 15, 2017 · 1 comment
Closed

Crash if closing ReactiveSocket immediately after opening it #308

lexs opened this issue Feb 15, 2017 · 1 comment

Comments

@lexs
Copy link
Contributor

lexs commented Feb 15, 2017

If you call ReactiveSocket::close() immediately after you've created it, it will crash in FrameTransport::onSubscribe() as the frameProcessor_ has been nulled out in close().
@lexs
Copy link
Contributor Author

lexs commented Feb 22, 2017

Fixed by 99bb29b

@lexs lexs closed this as completed Feb 22, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@lexs