Using the correct integer compression to get decompression working space size #2435
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.
Description of Change(s)
There is an issue in
_DecompressIntegers
function regarding dealing with integers bigger than 4 bytes. When dealing with integers bigger than 4 bytes, it is still usingUsd_IntegerCompression::GetDecompressionWorkingSpaceSize
to calculate the output buffer size where it should have usedUsd_IntegerCompression64::GetDecompressionWorkingSpaceSize
instead.This is the fix for this issue #2434
Fixes Issue(s)