alexcrichton opened PR #13070 from alexcrichton:zero-tables-manually to bytecodealliance:main:
In #12888 the failure of
madviseormmapwas improved to be handled in the pooling allocator but this only accounted for linear memories rather than tables as well. This meant that ifmadviseormmapfailed it could be possible to have the previous contents of one table leak over to the next. There's no known actual situation in which this would happen (madviseandmmapfailing is mostly theoretical) but this seems best to fix nonetheless.<!--
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 wasmtime-core-reviewers for a review on PR #13070.
alexcrichton requested dicej for a review on PR #13070.
pchickey submitted PR review.
alexcrichton added PR #13070 Improve madvise-failure logic in the pooling allocator to the merge queue.
alexcrichton merged PR #13070.
alexcrichton removed PR #13070 Improve madvise-failure logic in the pooling allocator from the merge queue.
Last updated: May 03 2026 at 22:13 UTC