search

pontem-network / pontem

🚀 Pontem Parachain node with Move VM onboard.
https://pontem.network
Apache License 2.0
77 stars 43 forks source link

Research why toolchain update breaks Pontem node #120

Closed borispovod closed 2 years ago

borispovod commented 2 years ago

Current node doesn't work correctly if we update toolchain, for example for 2021-09-12.

It's easy to check:

  1. Change toolchain to 2021-09-12 (use rust-toolchain file).
  2. Build node: make init && make build.
  3. Build polkadot.
  4. Use polkadot-launch to launch parachain and relay chain:
polkadot-launch ./launch-config.json

You will get error in Pontem node logs, like:

2021-10-21 13:45:00 [Parachain] :exclamation:️ Inherent extrinsic returned unexpected error: Error at calling runtime api: Execution failed: Other("Wasm execution trapped: wasm trap: out of bounds memory access\nwasm backtrace:\n    0: 0x574d5 - <unknown>!cumulus_pallet_parachain_system::relay_state_snapshot::RelayChainStateProof::new::h23864b3fb6168953\n    1: 0x1fe59d - <unknown>!<cumulus_pallet_parachain_system::pallet::Call<T> as frame_support::traits::dispatch::UnfilteredDispatchable>::dispatch_bypass_filter::h1c9f796bc215f2cf\n    2: 0x1f945f - <unknown>!<pontem_runtime::Call as frame_support::traits::dispatch::UnfilteredDispatchable>::dispatch_bypass_filter::h9c13df700fa219ef\n    3: 0x11db47 - <unknown>!<pontem_runtime::Call as sp_runtime::traits::Dispatchable>::dispatch::h923f320dc8bf608a\n    4: 0x1dcedd - <unknown>!frame_executive::Executive<System,Block,Context,UnsignedValidator,AllPallets,COnRuntimeUpgrade>::apply_extrinsic::hbb8e8c25e4649bb9\n    5: 0x21e849 - <unknown>!BlockBuilder_apply_extrinsic\nnote: run with `WASMTIME_BACKTRACE_DETAILS=1` environment variable to display more information\n"). Dropping.
borispovod commented 2 years ago

It doesn't happen recently, probably because to Polkadot/Substrate updates. I'm closing as out of date.