-
Notifications
You must be signed in to change notification settings - Fork 131
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
Westend crashes with wasm error: out of bounds memory access
at #9412261
#3509
Comments
The problem related to block rtConfig := wazero.NewRuntimeConfig().
WithMemoryCapacityFromMax(true).
WithMemoryLimitPages(23)
rt := wazero.NewRuntimeWithConfig(ctx, rtConfig)
_, err = rt.NewHostModuleBuilder("env").
ExportMemory("memory", 23). Executing block #9412261...
instance_test.go:482:
Error Trace: /Users/eclesiojunior/go/src/github.com/ChainSafe/gossamer/lib/runtime/wazero/instance_test.go:482
Error: Received unexpected error:
running runtime function: allocating: allocator out of space; failed to grow heap; heap.Grow ignored (recovered by wazero)
wasm stack trace:
env.ext_storage_get_version_1(i64) i64
.sp_io::storage::extern_host_function_impls::get::hf3b4edf587f8e8f1(i32,i32,i32)
.pallet_staking::pallet::pallet::Pallet<T>::eras_stakers::hdfb9a8654716e6b5(i32,i32,i32)
.<(TupleElement0,TupleElement1) as frame_support::traits::hooks::OnInitialize<BlockNumber>>::on_initialize::h8fe686fce2635624(i32) i64
.frame_executive::Executive<System,Block,Context,UnsignedValidator,AllPalletsWithSystem,COnRuntimeUpgrade>::initialize_block::h413dbea923e2629a(i32)
.Core_execute_block(i32,i32) i64 The above stacktrace is similar to the one describe in the issue #3509, however the difference is in the error: fyi @timwu20 @jimjbrettj |
Increasing the wasm page to
|
Describe the bug
The following stack trace was retrieved from a Gossamer staging node while syncing with Westend
The text was updated successfully, but these errors were encountered: