Stream: git-wasmtime

Topic: wasmtime / issue #10399 [gc] Panic: every on-stack gc_ref...

view this post on Zulip Wasmtime GitHub notifications bot (Mar 14 2025 at 13:19):

vouillon added the bug label to Issue #10399.

view this post on Zulip Wasmtime GitHub notifications bot (Mar 14 2025 at 13:19):

vouillon opened issue #10399:

Test Case

not-in-table.zip

Steps to Reproduce

Run the following command:

./target/debug/wasmtime  -W=all-proposals=y not-in-table.wasm

Expected Results

It should not crash.

Actual Results

We get a panic:

thread 'main' panicked at crates/wasmtime/src/runtime/vm/gc/enabled/drc.rs:239:13:
every on-stack gc_ref inside a Wasm frame should have an entry in the VMGcRefActivationsTable; 0x110 is not in the table

Versions and Environment

Wasmtime commit: a3381e48775912a3e1a68c05180932f3ce74c5b4

Operating system: Linux

Architecture: x64

view this post on Zulip Wasmtime GitHub notifications bot (Mar 21 2025 at 21:56):

vouillon commented on issue #10399:

This seems to be fixed by #10456

view this post on Zulip Wasmtime GitHub notifications bot (Mar 21 2025 at 22:00):

fitzgen commented on issue #10399:

You beat me to checking :)

view this post on Zulip Wasmtime GitHub notifications bot (Mar 24 2025 at 18:37):

cfallin closed issue #10399:

Test Case

not-in-table.zip

Steps to Reproduce

Run the following command:

./target/debug/wasmtime  -W=all-proposals=y not-in-table.wasm

Expected Results

It should not crash.

Actual Results

We get a panic:

thread 'main' panicked at crates/wasmtime/src/runtime/vm/gc/enabled/drc.rs:239:13:
every on-stack gc_ref inside a Wasm frame should have an entry in the VMGcRefActivationsTable; 0x110 is not in the table

Versions and Environment

Wasmtime commit: a3381e48775912a3e1a68c05180932f3ce74c5b4

Operating system: Linux

Architecture: x64

Last updated: Apr 18 2025 at 18:04 UTC