Fix framebuffer over release issue #268
Closed
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.
Hi, I'm developing an app with this amazing open library GPUImage2. Thanks to Bard.
But sometimes my app crashes due to framebuffer overrelease issue.
My app changes pipeline a lot. And this issue appears when pipeline is changed.
I tried to figure out this error and I found out that there is solution for this issue.
This PullRequest #243 explains what are the problems and solutions kindly. @joshbernfeld
But this pull request didn't merged because of unknown error, I guess.
So I make a pull request with core solution in #243.
And I test this code with my own app and it solves a problem.
I will wait for your comment.
Thanks.