-
Notifications
You must be signed in to change notification settings - Fork 2.6k
wasm trap: out of bounds memory access #14075
Comments
@yrong why did you close it? What was the issue? |
Hey @bkchr I'm going to cut a new ticket shortly with more details. This one was a bit light on details needed to troubleshoot the issue. |
BTW, this branch works for me. |
@bkchr So what's your rust version? I can reproduce the same error stack in both MacM1 and Ubuntu instance.
|
|
Exactly, resolved when upgrade rust to Btw, Is the rust version here safely to use for cumulus? Check the CI script here seems still |
With recent master you can now also use stable to compile the wasm binary. And yes, safe to upgrade. Please also close your stackexchange question. |
@vgeddes Seems no need to provide another ticket then. |
After upgrading rust toochain there is still a
More details found when debug with lldb something to do with
Again resolved when switch to @bkchr Since stack here and benchmark above all point to |
@yrong this should be: paritytech/parity-scale-codec#425 |
Is there an existing issue?
Experiencing problems? Have you tried our Stack Exchange first?
Description of bug
https://substrate.stackexchange.com/questions/8347/is-it-safe-to-use-const-generic-structure-in-runtime-storage
Steps to reproduce
For test we embed our bridge pallet into forked cumulus and link it as submodule, so after clone the repo above just update submodule and benchmark the pallet with command as following:
or I can just provide an ubuntu EC2 instance setup ready if nessessary.
The text was updated successfully, but these errors were encountered: