fix: reset capacity_ after ShareData and ShareDiff#7127
Open
Chessing234 wants to merge 1 commit into
Open
Conversation
After sharing memory with another blob, the local capacity is no longer valid for the shared buffer. Reset capacity_ to zero so a subsequent Reshape allocates fresh storage instead of reusing stale capacity. Fixes BVLC#5439. Co-authored-by: Cursor <cursoragent@cursor.com>
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Fixes #5439
Summary
After
ShareData()orShareDiff()shares memory with another blob, the localcapacity_no longer reflects the shared buffer. Reset it to zero so a laterReshape()allocates new storage instead of relying on stale capacity.Test plan
Made with Cursor