-
Notifications
You must be signed in to change notification settings - Fork 6
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
WASM exceed issue: Insufficient resources: memory minimum size of 2092 pages exceeds memory limits #27
Comments
it seems a runtime wasm including this is likely we are only using a fraction of the crate's functionality, so I wonder if there's a way to strip down all the unused code from the runtime wasm? There's a few interesting resources here: https://rustwasm.github.io/docs/book/reference/code-size.html Also dropping this on SE: https://substrate.stackexchange.com/questions/8443/prevent-unused-imports-from-bloating-up-runtime-wasm |
As discussed with @hbulgarini, he is able to reproduce the problem, but I am not. Instead, everything works fine and all parachains produce blocks without any issue. These are the wasm sizes I get when compiling trappist:
I don't really know which of the three is causing the issue, to be honest. Do you guys have any clue? |
what's the size of the trappist runtime without the chess pallet? |
Any updates with this issue? I want to help with it. |
Not really, since it was removed from trappist runtime we are not much diving into this project anymore. |
When the pallet is added in Trappist, the chain gets stalled and it stops producing blocks. Apparently, the error starts when the validators wants to run PoV function for the parachain:
2023-05-04 17:25:58 Failed to validate candidate para_id=Id(1836) error=InvalidCandidate(WorkerReportedError("execute: execute error: RuntimeConstruction(Other(\"failed to instantiate a new WASM module instance: Insufficient resources: memory minimum size of 2092 pages exceeds memory limits\"))"))
Tests were done running release 0.9.37 during the preparations for Trappist deployment on Rococo.
CC: @kalaninja
The text was updated successfully, but these errors were encountered: