exrcheck: assume lots of memory required whenever MultiPart ctor throws #915
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
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.
Fix https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=30249
Example file has a corrupt
typeattribute, which causes MultiPartInputFile ctor to throw, which bypasses the test for files which would take large amounts of memory during the single part input tests. The RgbaFile API does not throw for this file, but its width causes excessive memory allocation.This change reverses the sense of the test so every file which causes the MultiPartInputFile API to throw will be assumed to cause large amounts of memory to be used to read the file.
Signed-off-by: Peter Hillman peterh@wetafx.co.nz