Fix buffer usage #54461
Merged
Fix buffer usage #54461
+1
−1
Conversation
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
An array rented from the pool wasn't being properly size bound when used. Under some circumstances, the array pool would give back a larger array than needed, which would fail comparison to an array of the expected size. Replaced rental with an extension method that trims a Memory<byte> to the appropriate size, like all other code paths in the file.
jaschrep-msft
requested review from
amnguye,
jalauzon-msft,
nickliu-msft and
seanmcc-msft
as code owners
API Change CheckAPIView identified API level changes in this PR and created the following API reviews |
jalauzon-msft
approved these changes
Dec 12, 2025
jaschrep-msft
merged commit 863b690
into
Azure:feature/storage/stg101base
21 checks passed
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.
An array rented from the pool wasn't being properly size bound when used. Under some circumstances, the array pool would give back a larger array than needed, which would fail comparison to an array of the expected size.
Replaced rental with an extension method that trims a
Memory<byte>to the appropriate size, like all other code paths in the file.