alexcrichton opened PR #14586 from alexcrichton:requeue-work to bytecodealliance:main:
When a
run_concurrentfuture is dropped we'll properly clean up all resources associated with it, however Wasmtime will end up losing work if the store is resumed later and wasn't otherwise executing any wasm. This replaces the preexistingDrop-guard with one that re-enqueues the low-priority work into the store upon cancellation.<!--
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 wasmtime-core-reviewers for a review on PR #14586.
alexcrichton requested cfallin for a review on PR #14586.
github-actions[bot] added the label wasmtime:api on PR #14586.
fitzgen unassigned cfallin from PR #14586 Re-enqueue low priority items instead of dropping them.
fitzgen requested dicej for a review on PR #14586.
Last updated: Oct 11 2026 at 04:10 UTC