alexcrichton opened PR #13038 from alexcrichton:fix-shared-memory-panic to bytecodealliance:main:
This fixes a panic due to the
Instantdeadline not being representable when the timeout duration isDuration::MAX. The solution here is to usechecked_addand pretend there's no timeout on overflow since that's waiting long enough to effectively have no timeout. This is not reachable from WebAssembly as it can't represent long enough durations but is reachable via the embedder API. Additionally shared memories are gated by default, so this doesn't affect any default configuration.<!--
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 dicej for a review on PR #13038.
alexcrichton requested wasmtime-core-reviewers for a review on PR #13038.
dicej submitted PR review.
alexcrichton added PR #13038 Fix panic in atomic_wait{32,64} with massive timeouts to the merge queue.
alexcrichton merged PR #13038.
alexcrichton removed PR #13038 Fix panic in atomic_wait{32,64} with massive timeouts from the merge queue.
Last updated: Apr 12 2026 at 23:10 UTC