Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Wasmer 'assertion failed: prev.start > max' in wasmer-compiler-3.3.0/src/engine/trap/frame_info.rs:225:9 #1700

Closed
webmaster128 opened this issue May 31, 2023 · 3 comments
Labels
wasmer3/4 Changes related to the upgrade to Wasmer 3 and 4
Milestone

Comments

@webmaster128
Copy link
Member

When I run

while (cd packages/vm && cargo test) ; do :; done ; echo "Result from $(date)"

on main on my local machine, I get the following assertion failure after a few successful test runs:

thread 'cache::tests::save_wasm_fills_file_system_but_not_memory_cache' panicked at 'assertion failed: prev.start > max', ~/.cargo/registry/src/github.com-1ecc6299db9ec823/wasmer-compiler-3.3.0/src/engine/trap/frame_info.rs:225:9
note: run with RUST_BACKTRACE=1 environment variable to display a backtrace

Stack trace:

thread 'cache::tests::pin_unpin_works' panicked at 'assertion failed: prev.start > max', ~/.cargo/registry/src/github.com-1ecc6299db9ec823/wasmer-compiler-3.3.0/src/engine/trap/frame_info.rs:225:9
stack backtrace:
   0: rust_begin_unwind
             at /rustc/9eb3afe9ebe9c7d2b84b71002d44f4a0edac95e0/library/std/src/panicking.rs:575:5
   1: core::panicking::panic_fmt
             at /rustc/9eb3afe9ebe9c7d2b84b71002d44f4a0edac95e0/library/core/src/panicking.rs:64:14
   2: core::panicking::panic
             at /rustc/9eb3afe9ebe9c7d2b84b71002d44f4a0edac95e0/library/core/src/panicking.rs:114:5
   3: wasmer_compiler::engine::trap::frame_info::register
             at ~/.cargo/registry/src/github.com-1ecc6299db9ec823/wasmer-compiler-3.3.0/src/engine/trap/frame_info.rs:225:9
   4: wasmer_compiler::engine::artifact::Artifact::register_frame_info
             at ~/.cargo/registry/src/github.com-1ecc6299db9ec823/wasmer-compiler-3.3.0/src/engine/artifact.rs:397:21
   5: wasmer_compiler::engine::artifact::Artifact::instantiate
             at ~/.cargo/registry/src/github.com-1ecc6299db9ec823/wasmer-compiler-3.3.0/src/engine/artifact.rs:515:9
   6: wasmer::sys::module::Module::instantiate
             at ~/.cargo/registry/src/github.com-1ecc6299db9ec823/wasmer-3.3.0/src/sys/module.rs:142:39
   7: wasmer::sys::instance::Instance::new
             at ~/.cargo/registry/src/github.com-1ecc6299db9ec823/wasmer-3.3.0/src/sys/instance.rs:49:26
   8: wasmer::instance::Instance::new
             at ~/.cargo/registry/src/github.com-1ecc6299db9ec823/wasmer-3.3.0/src/instance.rs:69:33
   9: cosmwasm_vm::instance::Instance<A,S,Q>::from_module
             at ./src/instance.rs:247:17
  10: cosmwasm_vm::cache::Cache<A,S,Q>::get_instance
             at ./src/cache.rs:304:24
  11: cosmwasm_vm::cache::tests::pin_unpin_works
             at ./src/cache.rs:1178:25
  12: cosmwasm_vm::cache::tests::pin_unpin_works::{{closure}}
             at ./src/cache.rs:1172:26
  13: core::ops::function::FnOnce::call_once
             at /rustc/9eb3afe9ebe9c7d2b84b71002d44f4a0edac95e0/library/core/src/ops/function.rs:250:5
  14: core::ops::function::FnOnce::call_once
             at /rustc/9eb3afe9ebe9c7d2b84b71002d44f4a0edac95e0/library/core/src/ops/function.rs:250:5
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.

After a number of test runs, the following tests fail:

Test fail count
cache::tests::call_execute_on_cached_contract 3
cache::tests::call_instantiate_on_cached_contract 5
cache::tests::use_multiple_cached_instances_of_same_contract 2
cache::tests::pin_unpin_works 2
cache::tests::save_wasm_fills_file_system_but_not_memory_cache 2
cache::tests::resets_gas_when_reusing_instance 1
cache::tests::recovers_from_out_of_gas 1
instance::tests::memory_pages_returns_min_memory_size_by_default 1
cache::tests::get_instance_finds_cached_modules_and_stores_to_memory 2
@webmaster128 webmaster128 added this to the 1.3.0 milestone May 31, 2023
@webmaster128
Copy link
Member Author

The assertion hits here as well: pmndrs/swc-jotai#6 and pmndrs/swc-jotai#13

A bug report is open here: wasmerio/wasmer#3793

@chipshort
Copy link
Collaborator

This should be fixed now with the wasmer 4 update, right?

@webmaster128
Copy link
Member Author

Yes 🎉

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
wasmer3/4 Changes related to the upgrade to Wasmer 3 and 4
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants