alexcrichton opened PR #14741 from alexcrichton:fix-panic-when-future-dropped to bytecodealliance:main:
As the test illustrates, it's possible for such a future to be dropped when it has been queued to run (i.e. is no longer in the instance's
pendingset due to backpressure) but has not yet been run. Prior to this patch, that led to a panic inTypedFunc::call_async_concurrent::SignalDrop::drop. This addresses that by modifyingStoreOpaque::cancel_guest_subtask_without_lowered_parametersto look for and remove any matching tasks in the
ConcurrentState::high_priorityandConcurrentState::low_priorityqueues if they weren't found in thependingset.Part of https://github.com/bytecodealliance/wasmtime/security/advisories/GHSA-3r89-v5mq-j5xf
alexcrichton requested cfallin for a review on PR #14741.
alexcrichton requested wasmtime-core-reviewers for a review on PR #14741.
github-actions[bot] added the label wasmtime:api on PR #14741.
:thumbs_up: cfallin submitted PR review.
cfallin added PR #14741 avoid panic when call_async future dropped while queued to the merge queue.
:check: cfallin merged PR #14741.
cfallin removed PR #14741 avoid panic when call_async future dropped while queued from the merge queue.
Last updated: Oct 31 2026 at 23:03 UTC