-
-
Notifications
You must be signed in to change notification settings - Fork 62
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
MultiplexingStream.Dispose races with itself and throws NRE #129
Milestone
Comments
Yes: MultiplexingStream calls dispose on itself: What's more, it could protect the underlying stream from being disposed on two threads by just rearranging the order of these two lines: |
In fact I even caught the self-closing callstack as the NRE throwing stack in another occurrence:
|
AArnott
added a commit
that referenced
this issue
Oct 3, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When calling MultiplexingStream.Dispose I witnessed an NRE with this callstack:
The NRE would be caused by calling
BufferedStream.Dispose
concurrently on two threads. CouldMultiplexingStream
be responsible for calling Dispose on itself from another thread while we are calling Dispose on it? If so, we should ensure it's safe to call Dispose on it explicitly.The text was updated successfully, but these errors were encountered: