Added critical section to FMultiRegistry to make it thread-safe#7
Open
tinyogre wants to merge 1 commit intoAccelByte:mainfrom
Open
Added critical section to FMultiRegistry to make it thread-safe#7tinyogre wants to merge 1 commit intoAccelByte:mainfrom
tinyogre wants to merge 1 commit intoAccelByte:mainfrom
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Various login tasks access FMultiRegistry, which contains a static TMap<>. Those tasks run on worker threads, meaning that TMap<> was being both read from and modified by multiple threads at once, especially when logging in two PIE clients at the same time. This adds a critical section around all accesses to the map to make FMultiRegistry thread-safe.