Don't crash when an invalid TIFF file has no fields. #289
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
getID3 sometimes detects files as TIFF incorrectly, and then extracts no fields, causing a crash.
|
example file which triggers the bug. |
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.
getID3 sometimes detects files as TIFF incorrectly, and then extracts no fields, causing a crash.
(The file was a minimal example from https://stackoverflow.com/questions/57192090/minimal-audio-wav-or-mp3-file-in-bytes-for-unit-testing, and may not actually be a valid MP3 after all, but that isn't really important for the purpose of the fix).