Stream: git-wasmtime

Topic: wasmtime / issue #10464 GC: invalid VMGcKind with very la...

Wasmtime GitHub notifications bot (Mar 25 2025 at 00:34):

alexcrichton edited issue #10464:

As of 6a8d3d5a9ad32aa63cc39b657ec7352882dd5d70 this input:

(module
  (type $a (struct))
  (type $b (array structref))
  (start $c)
  (func $c
    struct.new_default $a
    i32.const 536870911
    array.new $b
    drop
  )
)

fails with:

$ cargo run -q -- -Wall-proposals foo.wat

thread 'main' panicked at /home/alex/code/wasmtime/crates/environ/src/gc.rs:394:18:
invalid `VMGcKind`: 0b10111000000000000000000000000000
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

Wasmtime GitHub notifications bot (Mar 25 2025 at 00:35):

fitzgen assigned fitzgen to issue #10464.

Wasmtime GitHub notifications bot (Mar 25 2025 at 01:20):

fitzgen commented on issue #10464:

Fixed after https://github.com/bytecodealliance/wasmtime/pull/10463, I suspect by the tracing changes and moving around of the object size limits stuff.

Will land this as a regression test after that PR lands.

Wasmtime GitHub notifications bot (Mar 26 2025 at 15:14):

fitzgen closed issue #10464:

As of 6a8d3d5a9ad32aa63cc39b657ec7352882dd5d70 this input:

(module
  (type $a (struct))
  (type $b (array structref))
  (start $c)
  (func $c
    struct.new_default $a
    i32.const 536870911
    array.new $b
    drop
  )
)

fails with:

$ cargo run -q -- -Wall-proposals foo.wat

thread 'main' panicked at /home/alex/code/wasmtime/crates/environ/src/gc.rs:394:18:
invalid `VMGcKind`: 0b10111000000000000000000000000000
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

Wasmtime GitHub notifications bot (Mar 26 2025 at 15:14):

fitzgen commented on issue #10464:

Fixed in eafe743, not sure why this issue didn't auto close.

Last updated: Apr 18 2025 at 12:05 UTC