alexcrichton requested wasmtime-core-reviewers for a review on PR #12976.
alexcrichton requested fitzgen for a review on PR #12976.
alexcrichton opened PR #12976 from alexcrichton:further-tweak-custom-page-sizes to bytecodealliance:main:
This commit adjust the behavior of #12884 to return -1 from
memory.growinstead of trapping when the growth would exceed the maximal allowable size of memory. This fixes a fuzz-bug which had an unexpected trap and upon further reflection this feels more accurate for what custom-page-sizes can do. With a 1-byte-page memories can grow to 4GiB-2 because that means that -1 always means "growth failed".<!--
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 added the label fuzz-bug on PR #12976.
fitzgen submitted PR review.
fitzgen added PR #12976 Further refine behavior of large 1-byte-page memories to the merge queue.
fitzgen merged PR #12976.
fitzgen removed PR #12976 Further refine behavior of large 1-byte-page memories from the merge queue.
Last updated: Apr 12 2026 at 23:10 UTC