-
Notifications
You must be signed in to change notification settings - Fork 496
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
NRE in 2.0.0 networking code #506
Comments
I believe this is a result of two competing Disconnected calls: for example an explicit Connect or Disconnect and a concurrent connection termination. I've locked the section around connection in Disconnected in e681328. This assumes that EventHandlers can't block eg by having an ExecutionContext (or is it SynchronizationContext?) associated that would try to dispatch Disconnected on another thread while blocking a Disconnect call. I need to figure out if this is indeed possible. |
Revised in 14d883b as a deadlock would have been possible when Disconnect holds connectionLock, waits for the setup task, and the setup task tries to call Disconnected. |
This is very likely the case, I got some extra details in the meantime.
My program simply tries to reconnect the moment it receives |
Anything still to be done here, or is this closable? |
Any chance we can get SK2 2.0.1 or 2.1.0-alpha shipped with this fix? I'd love to further test if anything new pops up, and if the issue is fixed, thanks! ❤️ |
I believe this is ready. |
This was reproduced on SK 2.0.0 (latest/final). I'm trying to get more details about this one in the meantime, since stacktrace is everything I have for now.
Thank you in advance and happy new year 🎉
The text was updated successfully, but these errors were encountered: