Search results

Failed CI build for refs/heads/release-36.0.0

Status: Open.

#13144 In bytecodealliance/wasmtime;

· github-actions opened on Apr 20, 2026

Uncaught segfault with GC tunables

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

Status: Open.

#13141 In bytecodealliance/wasmtime;

· alexcrichton opened on Apr 19, 2026

Add an optional typed interactive REPL for WebAssembly Components to the Wasmtime CLI

Status: Open.

#13136 In bytecodealliance/wasmtime;

· afsalthaj opened on Apr 19, 2026

Failed CI build for refs/heads/main

Status: Open.

#13135 In bytecodealliance/wasmtime;

· github-actions opened on Apr 18, 2026

potential gc fuzzbug: ASAN hits overflow and Segmentation fault

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

fuzz-bugBugs found by a fuzzerBugs found by a fuzzer

Status: Open.

#13134 In bytecodealliance/wasmtime;

· khagankhan opened on Apr 17, 2026

Per-function compilation diagnostics in cranelift_codegen should be trace, not debug

Status: Open.

#13133 In bytecodealliance/wasmtime;

· jspaith opened on Apr 17, 2026

Functions inherit_network and allow_ip_name_lookup are missing from c-api

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

Status: Open.

#13130 In bytecodealliance/wasmtime;

· gearhand opened on Apr 17, 2026

RUSTSEC-2026-0099: Name constraints were accepted for certificates asserting a wildcard name

Status: Open.

#13117 In bytecodealliance/wasmtime;

· github-actions opened on Apr 16, 2026

RUSTSEC-2026-0098: Name constraints for URI names were incorrectly accepted

Status: Open.

#13116 In bytecodealliance/wasmtime;

· github-actions opened on Apr 16, 2026

Should we define GC-related VM types in wasmtime-environ?

Status: Open.

#13114 In bytecodealliance/wasmtime;

· fitzgen opened on Apr 15, 2026

Deduplicate more code between DRC and copying GcCompiler implementations

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

Status: Open.

#13113 In bytecodealliance/wasmtime;

· fitzgen opened on Apr 15, 2026

Should accesses to the GC heap use MemFlags::trusted()?

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

Status: Open.

#13112 In bytecodealliance/wasmtime;

· fitzgen opened on Apr 15, 2026