Fix race between socket close and async calls by stream #1
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
karitra
approved these changes
May 21, 2018
|
|
||
| decoder_type m_decoder; | ||
|
|
||
| synchronized<bool> m_stopped{false}; |
There was a problem hiding this comment.
Could be generic std::atomic<bool> more convenient? The same for writable_stream.
Author
There was a problem hiding this comment.
std::atomic doesn't have RAII scope lock that is used in new code.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
The race leads to crash when streams try to concurrently perform asynchronous operation on closed socket.