wasmer run segfaults on current master branch

[fschutt]

$ ./target/release/wasmer run ./lib/c-api/examples/assets/qjs.wasm
zsh: segmentation fault  ./target/release/wasmer run ./lib/c-api/examples/assets/qjs.wasm

$ ./target/release/wasmer -vV
wasmer 3.1.0 (580ba 2023-01-20)
binary: wasmer-cli
commit-hash: 580baeb5090ab825d082e4d5dbcafb9e880d3e06
commit-date: 2023-01-20
host: aarch64-apple-darwin
compiler: singlepass,cranelift

I have no more context on this bug, but it's a full segfault, no panic trace given. Not sure if this is because of zsh interaction, but even when doing codesign -d -vvv --entitlements :- ./target/release/wasmer it doesn't work on Mac.

[fschutt]

This bug seems to be fine if you run it with --disable-cache. @ptitSeb reported problems on Linux:

target/release/wasmer run ./Lib/c-api/examples/assets/qjs.wasm

thread 'main' panicked at ‘assertion failed: !result.is_null()', /home/seb/.cargo/registry/src/github. con-lecc6299db9ec823/rkyv-0.7.39/src/impls/core/mod .rs:267:17

note: run with “RUST_BACKTRACE=1 environment variable to display a backtrace