Fixed crash caused by decodedImage in CCBufferedImageView being nil. #14
Conversation
This file contains 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
|
Thanks for the contribution 👍 (test failures are unrelated) |
neonichu
added a commit
that referenced
this pull request
Jan 25, 2016
Fixed crash caused by decodedImage in CCBufferedImageView being nil.
|
You welcome, thanks for the library! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
I've noticed that occasionally I get a crash when using CCBufferedImageView with progressive JPEGs. The crash is an EXC_BAD_ACCESS on the decodedImage variable in
public func connection(connection: NSURLConnection, didReceiveData data: NSData).This crash is quite easily reproducible if you place the CCBufferedImageView inside a tableview cell.
Adding a guard to make sure that decodedImage is not nil solves the issue.