[RC] Fix data race on gIsNewDatabase #15561
Open
+49
−2
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.
Fix #14715
Gemini's analysis:
✦ I've analyzed RCNConfigDBManager.m and confirmed gIsNewDatabase is accessed in RemoteConfigCreateFilePathIfNotExist and
isNewDatabase without proper synchronization. While dispatch_sync is present, the gIsNewDatabaseQueue is initialized too late
within sharedInstance. To fix this, I'll move the queue's initialization into a +load method, ensuring it's set up before any
other class methods are called. I will now apply this change.