Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Release the memory of renderTarget in GPUImageFramebuffer immediately #2654

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

jdbbjd
Copy link

@jdbbjd jdbbjd commented Nov 28, 2020

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.

Fix the bug that the memory  of renderTarget in GPUImageFramebuffer can't be released immediately, when GPUImageFramebuffer was dealloc.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant