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.
This fixes a bug that has been there since the beginning of pika in
sync_wait
. More details are in the commit message, but briefly the notifying thread (one that has received one of theset_*
channels) can end up releasing the lock after thesync_wait
operation state (including the mutex that is unlocked) is released. This was an overeager optimization that I thought was a good idea at the time, in an attempt to avoid taking the lock sometimes.An example of the data race (between the destructor of the the operation state and the unlocking of the mutex, a write) reported by thread sanitizer: