Issue #11251 panic using future.{read,write} with no type and no memory was transferred from bytecodealliance/wasip3-prototyping#235.
dicej commented on issue #11251:
Thanks for reporting this @lukewagner. I've moved the issue to the Wasmtime repo since CM async support has been upstreamed (and thus this should be reproduceable on the latest canary build).
dicej assigned dicej to issue #11251.
dicej added the wasm-proposal:component-model-async label to Issue #11251.
dicej edited a comment on issue #11251:
Thanks for reporting this @lukewagner. I've moved the issue to the Wasmtime repo since CM async support has been upstreamed (
and thus this should be reproduceable on the latest canary buildEr, maybe we don't have canary builds in this repo; the lastdevbuild appears to be from 2022).
alexcrichton removed the bug label from Issue #11251.
alexcrichton closed issue #11251:
To reproduce, start with this test:
https://github.com/WebAssembly/component-model/blob/main/test/async/empty-wait.wast
and then delete the(memory $memory "mem")on either thecanon future.readorcanon future.write.Backtrace:
$ RUST_BACKTRACE=full wasmtime-p3 wast -W component-model-async=yes empty-wait.wast thread '<unnamed>' panicked at crates/cranelift/src/compiler/component.rs:1317:70: called `Option::unwrap()` on a `None` value stack backtrace: 12: 0x107bbba08 - core::option::unwrap_failed::hdbf5b02c13e4fbf7 13: 0x106e26729 - wasmtime_internal_cranelift::compiler::component::TrampolineCompiler::translate_future_or_stream_call::h5f2f561f1bc4b0c3 14: 0x106e80d9c - wasmtime_internal_cranelift::compiler::component::<impl wasmtime_environ::component::compiler::ComponentCompiler for wasmtime_internal_cranelift::compiler::Compiler>::compile_trampoline::{{closure}}::h92a0b1bc7be14058
Last updated: Dec 06 2025 at 06:05 UTC