alexcrichton opened PR #14557 from alexcrichton:improve-drop-async to bytecodealliance:main:
This commit fixes a few issues when an async computation (a future) was dropped/cancelled on the host. This could lead to
bail_bug!being hit in a number of locations which shouldn't be possible to hit. The general idea here is to lock down the store in a few more locations, for example cancelling a fiber, and then additionally shuffling around code around instantiation to move it to where it can't be interrupted viadrop(no await points between the significant portions).<!--
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 review the Bytecode Alliance's AI tool usage policy at
https://github.com/bytecodealliance/governance/blob/main/AI_TOOL_POLICY.mdPlease ensure all communication follows the code of conduct:
https://github.com/bytecodealliance/wasmtime/blob/main/CODE_OF_CONDUCT.md
-->
alexcrichton requested pchickey for a review on PR #14557.
alexcrichton requested wasmtime-core-reviewers for a review on PR #14557.
github-actions[bot] added the label wasmtime:api on PR #14557.
:thumbs_up: pchickey submitted PR review.
alexcrichton added PR #14557 Fix some store behavior when dropping async computations to the merge queue.
:check: alexcrichton merged PR #14557.
alexcrichton removed PR #14557 Fix some store behavior when dropping async computations from the merge queue.
Last updated: Oct 11 2026 at 04:10 UTC