Reduce committed bytes if mark array commit fails#106400
Merged
cshung merged 1 commit intodotnet:mainfrom Aug 23, 2024
Merged
Conversation
Maoni0
approved these changes
Aug 22, 2024
Member
|
please do add a description of what the issue is and how your fix fixes the problem. |
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Problem:
In case the GC tries to create a new segment, it might succeed to commit the new card table part for it but fail to commit the mark arrays, as such, we will virtual free the full range so every thing (card table and mark array) are decommitted, but commit accounting is not reducing the bytes there.
Since the range is decommitted, this has only debug impact.
Fixes #102706