Stream: git-wasmtime

Topic: wasmtime / issue #13173 More uncaught segfaults with GC t...

Wasmtime GitHub notifications bot (Apr 22 2026 at 19:48):

alexcrichton assigned fitzgen to issue #13173.

Wasmtime GitHub notifications bot (Apr 22 2026 at 19:48):

alexcrichton opened issue #13173:

Although the problems on https://github.com/bytecodealliance/wasmtime/issues/13141 are all fixed it looks like some remaining issues linger in OSS-Fuzz, still reproducible on main. I believe these are as-yet-novel and as-yet-unfixed, so posting here too. These fuzz inputs all currently still crash:

gc_ops2.txt
gc_ops1.txt
call_async2.txt
call_async1.txt

Wasmtime GitHub notifications bot (Apr 22 2026 at 19:48):

alexcrichton added the fuzz-bug label to Issue #13173.

Wasmtime GitHub notifications bot (Apr 22 2026 at 19:48):

alexcrichton added the wasm-proposal:gc label to Issue #13173.

Wasmtime GitHub notifications bot (Apr 24 2026 at 14:39):

alexcrichton commented on issue #13173:

Another segfault, this time in Pulley, what I assume is likely related -- gc_ops3.txt

Wasmtime GitHub notifications bot (Apr 24 2026 at 19:20):

fitzgen closed issue #13173:

Although the problems on https://github.com/bytecodealliance/wasmtime/issues/13141 are all fixed it looks like some remaining issues linger in OSS-Fuzz, still reproducible on main. I believe these are as-yet-novel and as-yet-unfixed, so posting here too. These fuzz inputs all currently still crash:

gc_ops2.txt
gc_ops1.txt
call_async2.txt
call_async1.txt

Last updated: May 03 2026 at 22:13 UTC