Logging: fix race in disposal of a passed-in TextWriter #2581
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Occasionally we'd see
chunkLength
errors fromStringWriter
.ToString()
calls after connecting. I think we've isolated this (via test stress runs) down to a write happening post-lock on theTextWriterLogger
disposal. This lock in dispose ensures we're not trying to write to a writer we should have fully released at the end of a.Connect()
/.ConnectAsync()
call.