prevent integer overflow in DeepScanlineInputFile with huge images #1261
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.
Address an overflow allocating sample count table in DeepScanLineInputFile (issue found by Nick C)
When there are more than 2^29 pixels in an image, the table allocation overflows, causing incorrect memory allocation of the table. Switching storage from Array to std::vector would allow for larger images, but the limit seems a reasonable one, so instead an explicit check for overflow is added. Larger images should still be readable using the core API (or, better still, written using the deeptile API)
Signed-off-by: Peter Hillman peterh@wetafx.co.nz