fitzgen opened PR #10589 from fitzgen:add-capacity-not-enough-for-first-alloc to bytecodealliance:main:
When we haven't added enough capacity such that it is greater than or equal to our alignment, we were triggering a debug assertion and would get integer overflow and a corrupted free list in release builds. Note that, due to our GC heap sandboxing, this couldn't lead to anything worse than a panic/abort.
<!--
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
-->
fitzgen requested pchickey for a review on PR #10589.
fitzgen requested wasmtime-core-reviewers for a review on PR #10589.
pchickey submitted PR review.
fitzgen has enabled auto merge for PR #10589.
fitzgen merged PR #10589.
Last updated: Dec 06 2025 at 06:05 UTC