reduce B44 _tmpBufferSize (was allocating two bytes per byte) #843
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.
B44 was allocating a _tmpBuffer of
maxScanLineSize
*numScanlines
unsigned short
values.maxScanLineSize
is the number of bytes of uncompressed data on each scanline, not the number of pixel samples. _tmpBuffer was therefore assigning one 16 bit short for every byte of uncompressed data, so making the buffer twice the size it needs to bepartially addresses out-of-memory issue https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=25913
Signed-off-by: Peter Hillman peterh@wetafx.co.nz