Fix ImageReader crash when accessing Image buffer #119
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
…Format.KEY_COLOR_FORMAT` to `CodecCapabilities.COLOR_FormatYUV420Flexible` corresponding to `ImageFormat.YUV_420_888` for extraction.
|
Thank you for this PR. There are two reasons why it's not merged yet:
I'm keeping it open to collect additional feedback. |
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.
WHAT
When
setSurfacewith a ImageReader surface, theMediaFormat.KEY_COLOR_FORMAThas to correspond to ImageReader's format. If not set, some codec will uses default not compatible withImageFormat.YUV_420_888and causes crash similar to https://ittone.ma/ittone/android-jni-detected-error-in-application-non-zero-capacity-for-nullptr-pointer-1/Commits
MediaFormat.KEY_COLOR_FORMATtoCodecCapabilities.COLOR_FormatYUV420Flexiblecorresponding toImageFormat.YUV_420_888for extraction.