Fix the bug that heif_image_release will release the bitmap buffer before CGImage dealloc and cause crash #12
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
…before CGImage dealloc and cause crash. This only happened on real iPhone device but not simulator
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.
See #11
This only happened on real iPhone device but not simulator.
This is because of the wrong implementation of #10 .
heif_image_release, will do afreecall to the bitmap buffer. At that time I only test the iPhone Simulator, but not real device. So I found it's OK.However, the better solution, it's to use the
CGDataProviderCreateWithDatatheinfoarg. We need to pass theheif_imageopaque pointer, and then using the API to release the bitmap buffer. So this always correct.