Fix raster exception from malformed WebP images#107
Merged
Conversation
lucianbc
force-pushed
the
lucianbc/fix-raster-exception
branch
2 times, most recently
from
ddbab05 to
0051068
Compare
Some WebP images cannot be parsed by the ImageIO plug in. They probably have a malformed frame header, but the actual rendering algorithm handles this issue gracefully and can still draw the images. Howerver, the memory footprint tool crashes for such images. When such an exception occurs, we can avoid crashing by assuming the frame is fully white, which may lead to a bigger memory footprint, but the watch face may still pass the check, or fail with a known error.
lucianbc
force-pushed
the
lucianbc/fix-raster-exception
branch
from
0051068 to
5b98f7d
Compare
robcos
approved these changes
Apr 8, 2026
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
2 participants
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.
Some WebP images cannot be parsed by the ImageIO plug in. They probably have a malformed frame header, but the actual rendering algorithm handles this issue gracefully and can still draw the images. Howerver, the memory footprint tool crashes for such images. When such an exception occurs, we can avoid crashing by assuming the frame is fully white, which may lead to a bigger memory footprint, but the watch face may still pass the check, or fail with a known error.