Fix too early writebarrier in tally_up #13629
Merged
+3
−2
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
2F69
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.
This is a "too early" write barrier which I found this using my wbcheck tool (See #13557). I added an option to re-verify objects on the first possible GC after they have a write barrier.
So what could have happened is:
st_update
realizes it needs to resize the table, and so allocates. This triggers GC which incrementally markshash
, butgroup
has not yet been writtengroup
are never marked and freed, andgroup
is never marked