Use atomic variables for ConnectionInterrupted and LBQ currentSize #100
No reviewers
Labels
No labels
bug
dependencies
duplicate
enhancement
hacktoberfest-accepted
invalid
question
submodules
wontfix
No milestone
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
gh-moonlight-stream/moonlight-common-c!100
Loading…
Reference in a new issue
No description provided.
Delete branch "andygrundman/andyg.atomic-fixes"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
These were the only two variables reported by clang's -fsanitize=thread. I was testing the iOS app in Xcode and didn't test that many code paths, but these 2 were straightforward to fix.
For as often as currentSize gets touched, it's never caused a problem for me, so I doubt these have ever caused crashes for anyone. Maybe technically, in theory they could have.
Yeah, I tried a while back to make this code TSan clean. Unfortunately we will run into the fact that C11 atomics aren't well supported on MSVC. Last I saw, they are supported with only an experimental compiler flag (
/experimental:c11atomics). I just gave it a try with the latest VS 17.12.3 and it still requires the experimental flag :(View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.Merge
Merge the changes and update on Forgejo.Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.