Fix the issue when WebP is static webp, the SDAnimatedImageCoder
protocol implementation still create CGContext, this can reduce RAM usage #30
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 is a quick fix for #29.
For Static WebP, we don't create extra CGContext to consume RAM. Instead, just do the static WebP decoding.
Note this method still need to be protected in the LOCK/UNLOCK code, because multiple thread can access the
animatedImageFrameAtIndex:
, and we share the global_demux
instance.The root solution is in 5.4.2 of SDWebImage, see: SDWebImage/SDWebImage#2924