Search results

[wasi-io] polling (p2) or waitable-set.waiting (p3) with a zero timeout can starve the async runtime

bugIncorrect behavior in the current implementation that needs fixingIncorrect behavior in the current implementation that needs fixing

wasi:implIssues pertaining to WASI implementation in WasmtimeIssues pertaining to WASI implementation in Wasmtime

Status: Open.

#13040 In bytecodealliance/wasmtime;

· dicej opened on Apr 10, 2026

Passing GC objects multiple times to wasm can cause leaks/refcount corruption

wasm-proposal:gcIssues with the implementation of the gc wasm proposalIssues with the implementation of the gc wasm proposal

Status: Open.

#13037 In bytecodealliance/wasmtime;

· alexcrichton opened on Apr 10, 2026

Large constant GC array causes runtime panics in a few ways

wasm-proposal:gcIssues with the implementation of the gc wasm proposalIssues with the implementation of the gc wasm proposal

Status: Open.

#13034 In bytecodealliance/wasmtime;

· alexcrichton opened on Apr 10, 2026

Stack-switching crash with traps and missing bounds checks

wasm-proposal:stack-switchingIssues related to WebAssembly stack switchingIssues related to WebAssembly stack switching

Status: Open.

#13028 In bytecodealliance/wasmtime;

· alexcrichton opened on Apr 9, 2026

Fixed length lists in FACT don't handle the memory64 proposal

wasm-proposal:component-modelIssues related to the WebAssembly Component Model proposalIssues related to the WebAssembly Component Model proposal

Status: Open.

#13025 In bytecodealliance/wasmtime;

· alexcrichton opened on Apr 9, 2026

Futures/streams don't fully validate the item limit of 1<<28 items

wasm-proposal:component-model-asyncIssues related to the WebAssembly Component Model async proposalIssues related to the WebAssembly Component Model async proposal

Status: Open.

#13023 In bytecodealliance/wasmtime;

· alexcrichton opened on Apr 9, 2026

Compilation panic with array of contref

wasm-proposal:stack-switchingIssues related to WebAssembly stack switchingIssues related to WebAssembly stack switching

Status: Open.

#13022 In bytecodealliance/wasmtime;

· alexcrichton opened on Apr 9, 2026

Missing contref handling in VMArrayRef::read_elem

wasm-proposal:stack-switchingIssues related to WebAssembly stack switchingIssues related to WebAssembly stack switching

Status: Open.

#13021 In bytecodealliance/wasmtime;

· alexcrichton opened on Apr 9, 2026

VMContinuationStack::initialize likely wants some defense-in-depth bounds checks

wasm-proposal:stack-switchingIssues related to WebAssembly stack switchingIssues related to WebAssembly stack switching

Status: Open.

#13020 In bytecodealliance/wasmtime;

· alexcrichton opened on Apr 9, 2026

Using n in LLDB seems to equate to continue

wasmtime:debuggingIssues related to debugging of JIT'ed codeIssues related to debugging of JIT'ed code

Status: Open.

#12995 In bytecodealliance/wasmtime;

· alexcrichton opened on Apr 9, 2026

c-api: wasmtime_call_future_poll uses Waker::noop()

wasmtime:c-apiIssues pertaining to the C API.Issues pertaining to the C API.

Status: Open.

#12991 In bytecodealliance/wasmtime;

· chaynabors opened on Apr 8, 2026

Support Limiting of Host Heap Usage when using ResourceTable

Status: Open.

#12984 In bytecodealliance/wasmtime;

· posborne opened on Apr 7, 2026