HTML5: fix various crashes with image files - #923
Merged
Conversation
Failed image loads now yield an empty display object like other platforms instead of crashing.
Shchvova
approved these changes
Jun 11, 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.
Currently HTML5 builds crash if they handle .jpg/.jpeg images. Additionally, while I was testing the Add display.isValidObject function feature, I found that HTML5 builds detect invalid/corrupted image files, but instead of just logging an error, like on other platforms, they just crash.
The sample project contains 6 valid image files and 16 invalid/corrupted image files. It'll work with these changes, but instantly crash on current HTML5 builds:
html5-build-errors.zip