Trigger GC in the DRC collector when the OASR list is twice the size it was after the last GC#13422
Merged
fitzgen merged 4 commits intoMay 21, 2026
Conversation
github-actions
Bot
added
wasmtime:api
Subscribe to Label Actioncc @fitzgen DetailsThis issue or pull request has been labeled: "wasmtime:api", "wasmtime:ref-types"Thus the following users have been cc'd because of the following labels:
To subscribe or unsubscribe from this label, edit the |
cfallin
approved these changes
May 20, 2026
…it was after the last GC This should trigger collection in more situations than just filling up the heap from allocation. Fixes bytecodealliance#13403 in theory, but I haven't been able to measure sweep times reported in that issue without this fix on my laptop. FWIW, that issue does refer to Android, and so is probably using radically different hardware.
fitzgen
force-pushed
the
wasmtime-drc-over-approx-force-gc
branch
from
e403269 to
734fab6
Compare
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
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.
This should trigger collection in more situations than just filling up the heap from allocation.
Fixes #13403 in theory, but I haven't been able to measure sweep times reported in that issue without this fix on my laptop. FWIW, that issue does refer to Android, and so is probably using radically different hardware.