Wasmtime GitHub notifications bot (Feb 19 2026 at 15:42): Wasmtime GitHub notifications bot (Feb 19 2026 at 15:42):alexcrichton opened PR #12625 from alexcrichton:no-panic-on-oom to bytecodealliance:main:
For no_std scenarios gracefully handle allocation failure like OS-level failures are handled and propagate the error upwards.
<!--
Please make sure you include the following information:
If this work has been discussed elsewhere, please include a link to that
conversation. If it was discussed in an issue, just mention "issue #...".Explain why this change is needed. If the details are in an issue already,
this can be brief.Our development process is documented in the Wasmtime book:
https://docs.wasmtime.dev/contributing-development-process.htmlPlease ensure all communication follows the code of conduct:
https://github.com/bytecodealliance/wasmtime/blob/main/CODE_OF_CONDUCT.md
-->
Wasmtime GitHub notifications bot (Feb 19 2026 at 15:42):alexcrichton requested fitzgen for a review on PR #12625.
Wasmtime GitHub notifications bot (Feb 19 2026 at 15:42):alexcrichton requested wasmtime-core-reviewers for a review on PR #12625.
Wasmtime GitHub notifications bot (Feb 19 2026 at 16:04):fitzgen submitted PR review:
Thanks!
Wasmtime GitHub notifications bot (Feb 19 2026 at 16:04):fitzgen added PR #12625 Don't panic on OOM when allocating MmapVec to the merge queue
Wasmtime GitHub notifications bot (Feb 19 2026 at 16:28):fitzgen merged PR #12625.
Wasmtime GitHub notifications bot (Feb 19 2026 at 16:28):fitzgen removed PR #12625 Don't panic on OOM when allocating MmapVec from the merge queue
Last updated: Feb 24 2026 at 04:36 UTC