Add thread safety to WIC initialization using call_once #807
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
3 participants
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.
Technically the singleton DefaultWicAdapter instance was not thread-safe when creating the WIC factory. Similarly, the DefaultCanvasImageAdapter was not thread-safe when storing a copy of the WicAdapter instance. In the second case in practice it probably was thread-safe anyway assuming setting a pointer is atomic. In the first case it would probably have been very difficult to hit a serious issue, although potentially it could have leaked the factory object and potentially returned a different instance on different calls.
This pull request fixes that by using std::call_once.