-
Notifications
You must be signed in to change notification settings - Fork 452
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
Token balance graph error #5255
Comments
This is also reported by a user at the forum. |
I can't seem to reproduce this issue on Mac, by plotting some basic time series. @synctext To further debug this, I need the |
I tried to reproduce this issue on Mac, but it does not seem to trigger with the database provided by @synctext: I also digged into the code to verify that the blocks are being delivered to the GUI in order, which seems to be the case. There are also no bandwidth inconsistencies in the block data (e.g., the total up of a subsequent block is lower) which could lead to this behavior. The bug also does not trigger on our Ubuntu 18.04 testing machine. This bug report about the magical error in stdout seems to indicate that it is a problem with the GTK3 backend, and therefore outside our reach to fix. I haven't received any similar reports of this issue on non-Linux machines yet. When Ubuntu 20.04 is released (later this month), I will see if I can reproduce the error with that OS. For now, I am postponing this issue to a later milestone since I am unable to reproduce it, and it seems to be specific to Ubuntu. |
Something similar happening on Manjaro with 7.4.4: #5199 (comment) |
Reproduced with 7.5.0RC6: key event is that my laptop was in sleep mode for a few hours and glitch seemed to happen after a resume and or offline period. Could be a stale packet problem, old peer cache something, clock issue, database default counter or just a complete coincidence. Sleep times and period disconnected from Internet of laptop are clearly visible. Zoom on glitch: |
Somehow the first and last datapoint is connected with 2nd "Bytes taken" line.
The text was updated successfully, but these errors were encountered: