I have fixed the bug #76 #86
Open
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
Author
|
Hi, I’ve opened a PR fixing this issue: #86. |
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.
This PR introduces a thread-safe initialization mechanism for SingletonBase to prevent race conditions during concurrent object creation. The implementation follows a double-checked locking pattern to ensure correctness and minimize unnecessary synchronization overhead.
The previous implementation was vulnerable to race conditions because multiple threads could enter call simultaneously and each create its own instance.
This led to:
inconsistent singleton state
potential corruption of shared resources
unpredictable behavior during parallel execution
The new implementation ensures exactly one instance is created—even under high concurrency—without introducing unnecessary overhead.