Transfer ownership of returned CF objects to avoid memory leak#196
Open
wxxion wants to merge 1 commit intokishikawakatsumi:masterfrom
Open
Transfer ownership of returned CF objects to avoid memory leak#196wxxion wants to merge 1 commit intokishikawakatsumi:masterfrom
wxxion wants to merge 1 commit intokishikawakatsumi:masterfrom
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.
According to Apple doc, it's the responsibility of caller of SecAccessControlCreateWithFlags and SecItemCopyMatching to release the returned CF object. So we should
__bridge_transferthe ownership to corresponding Objective-C object to manage the memory with ARC.