This repository has been archived by the owner on Nov 15, 2023. It is now read-only.
Dangerously long stack trace when syncing a new node #8950
Labels
I3-bug
The node fails to follow expected behavior.
I was doing some memory profiling over the weekend, and over the course of 60h of profiling I've got this stack trace that was 5763 frames long:
The
<sp_state_machine::ext::Ext<H,N,B> as sp_externalities::Externalities>::next_storage_key
appears 5693 times in total in this stack trace; looks like unbound recursion.This happened during a fresh sync of a new node on Kusama, with interpreted WASM execution, with freshly compiled
polkadot
fromf0ce0ca1f8b03d5ad3b80ce66793f18bde21cd14
.Probably the same issue as #4527 if I'd had to guess.
The text was updated successfully, but these errors were encountered: