Release the memory of renderTarget in GPUImageFramebuffer immediately #2654
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.
When I use GPUImage and AVMutableVideoComposition.customVideoCompositorClass to process 4K videos, there will be much large size GPUImageFramebuffer cached in GPUImageFramebufferCache. When I use GPUImageFramebufferCache 's purgeAllUnassignedFramebuffers to release all the GPUImageFramebuffer, the GPUImageFramebuffer will dealloc immediately, then the renderTarget in GPUImageFramebuffer will be released, but the memory of renderTarget was not released, so my app always crash easily. Then I found that if I create texture without CVOpenGLESTextureCacheCreateTextureFromImage, the memory of renderTarget can be released immediately, and Now I found a new function in iOS 11.0, which can also create a texture with IOSurface, and the the memory of renderTarget can be released immediately too.