-
Notifications
You must be signed in to change notification settings - Fork 992
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
tui logs tab causing panic #3138
Comments
There must be a race condition or some kind of timing issue during startup - I can't reproduce it now using either a It's really weird. Are we assuming something is initialized during tui startup (say the logging infrastructure) but it may not be guaranteed to be? Either way I think the |
I ran into a similar issue when syncing. I stumbled over this ticket when searching for a solution. Since my problem seems to be related I post here, please ping me if you want this in a new ticket. I got this error repeatedly in the initial fast-sync, in step 2. Here are the logs of one run:
It seems it was related to the timeout that kicks in after 10 minutes. Eventually I was connected to peers with who I had a better bandwidth - once I could pass the syncing step 2 the problem was gone. Since then the client has just been running steadily. As visible from the log: |
@da-kami Thanks for reporting that panic, I've opened a PR that fixes it |
Not entirely sure what causes this to occur but I'm able to reproduce this locally reliably in debug mode.
Its happening here -
So it appears
p.size.y
is0
and we try and subtract from it, going negative.Fixable with a
saturating_sub()
but not sure what the actual reason for this happening is.I'll put a PR up to fix this. But might be worth investigating what caused this to happen.
The text was updated successfully, but these errors were encountered: