-
Notifications
You must be signed in to change notification settings - Fork 74
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
Smoldot freezes browser UI on sync finish #2786
Comments
This is most likely the time it takes to verify the finality proofs. While there's a "CPU limiter" in place, I suspect that it doesn't work because the inner |
@tomaka thanks for the fix, can't wait to see it merged and released |
mergify bot
added a commit
that referenced
this issue
Oct 4, 2022
Fix #2786 Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In our SPA we use
@polkadot/rpc-provider^9.4.2
to connect 3ScProviders
During the connection UI works fine, but just before
sync finished
message in console we face a 1.2 second freeze.This happens every time when
sync finished
for 3 chains that we connect with ScProvider - Polkadot, Kusama, Westend.We're not sending any requests to ScProvider, it just works by itself.
I recorded performance check in Chrome and saw a long wasm function execution
Log message example: [sync-service-polkadot] GrandPa warp sync finished to #12229848 (0xea75…6e7b)
smoldot version 0.6.34
The text was updated successfully, but these errors were encountered: