Skip to content

Re-enqueue low priority items instead of dropping them - #14586

Open
alexcrichton wants to merge 1 commit into
bytecodealliance:mainfrom
alexcrichton:requeue-work
Open

alexcrichton wants to merge 1 commit into
bytecodealliance:mainfrom
alexcrichton:requeue-work

Conversation

@alexcrichton

Copy link
Copy Markdown
Member

When a run_concurrent future 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 preexisting Drop-guard with one that re-enqueues the low-priority work into the store upon cancellation.

When a `run_concurrent` future 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 preexisting `Drop`-guard with one that re-enqueues the
low-priority work into the store upon cancellation.
@alexcrichton
alexcrichton requested a review from a team as a code owner October 6, 2026 20:23
@alexcrichton
alexcrichton requested review from cfallin and removed request for a team October 6, 2026 20:23
@github-actions github-actions Bot added the wasmtime:api Related to the API of the `wasmtime` crate itself label Oct 6, 2026
@fitzgen
fitzgen requested review from dicej and removed request for cfallin October 8, 2026 16:49

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

wasmtime:api Related to the API of the `wasmtime` crate itself

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant