alexcrichton opened PR #13579 from alexcrichton:fix-pooling-allocator-oom to bytecodealliance:main:
This commit fixes an issue where if the pooling allocator generated OOM at just the right time then it would leave the pooling allocator in a corrupt state where the instance count was incremented, never decremented. This additionally fixes a separate issue where if an OOM happened just a bit later then it would mean that tables/memories from the pooling allocator would leak and not be properly destroyed within the allocator, leaking their slots.
<!--
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
-->
alexcrichton requested fitzgen for a review on PR #13579.
alexcrichton requested wasmtime-core-reviewers for a review on PR #13579.
alexcrichton requested wasmtime-fuzz-reviewers for a review on PR #13579.
:thumbs_up: fitzgen submitted PR review:
Oo nice find
fitzgen added PR #13579 Fix corrupted pooling allocator state on OOM to the merge queue.
alexcrichton removed PR #13579 Fix corrupted pooling allocator state on OOM from the merge queue.
alexcrichton added PR #13579 Fix corrupted pooling allocator state on OOM to the merge queue.
:check: alexcrichton merged PR #13579.
alexcrichton removed PR #13579 Fix corrupted pooling allocator state on OOM from the merge queue.
Last updated: Jul 29 2026 at 05:03 UTC