Add docs for OOM-handling in Wasmtime#13224
Merged
fitzgen merged 3 commits intobytecodealliance:mainfrom Apr 28, 2026
Merged
Conversation
And use this as a place to document which portions of Wasmtime attempt to handle OOM, how to enable `cfg(arc_try_new)` to handle more OOMs with a nightly rust toolchain, and clarify that OOM handling is not tier 1.
cfallin
approved these changes
Apr 28, 2026
Member
cfallin
left a comment
cfallin
left a comment
There was a problem hiding this comment.
Generally looks great -- thanks for documenting all of this!
(I didn't check the exact correspondence of where you added the # Errors subsections to which functions should have then but I spot-checked, and trust that you carefully lined those up)
Only a few thoughts on the table below...
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.
Part of #12069