Skip to content
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

Closed
synctext opened this issue Mar 28, 2020 · 9 comments · Fixed by #5626
Closed

Token balance graph error #5255

synctext opened this issue Mar 28, 2020 · 9 comments · Fixed by #5626

Comments

@synctext
Copy link
Member

Somehow the first and last datapoint is connected with 2nd "Bytes taken" line.
Screenshot from 2020-03-28 13-12-08

@synctext synctext added this to the V7.5: core refactoring milestone Mar 28, 2020
@ichorid
Copy link
Contributor

ichorid commented Mar 28, 2020

This is also reported by a user at the forum.

@devos50
Copy link
Contributor

devos50 commented Mar 29, 2020

I can't seem to reproduce this issue on Mac, by plotting some basic time series.

@synctext To further debug this, I need the trustchain.db in the sqlite directory of your Tribler state directory. Furthermore, I need your public key, which you can find by going to the debug pane -> Trustchain. A screenshot should suffice 👍

@triblerteam
Copy link
Member

fixed!
Screenshot from 2020-04-02 15-26-36

@synctext synctext reopened this Apr 2, 2020
@synctext
Copy link
Member Author

synctext commented Apr 2, 2020

Back :-) emailing... Gem in the debug:

*** BUG ***
In pixman_region32_init_rect: Invalid rectangle passed
Set a breakpoint on '_pixman_log_error' to debug

Screenshot from 2020-04-02 19-40-23

@synctext
Copy link
Member Author

synctext commented Apr 3, 2020

Using resize and zoom:
Screenshot from 2020-04-03 10-38-13

@devos50
Copy link
Contributor

devos50 commented Apr 3, 2020

I tried to reproduce this issue on Mac, but it does not seem to trigger with the database provided by @synctext:

Schermafbeelding 2020-04-03 om 11 33 17

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.

@MeadowHillSoftware
Copy link

MeadowHillSoftware commented Apr 5, 2020

Something similar happening on Manjaro with 7.4.4: #5199 (comment)

@synctext
Copy link
Member Author

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:

Screenshot from 2020-06-17 10-13-18
And the broader picture on overall wallet:
Screenshot from 2020-06-17 10-12-22

@devos50
Copy link
Contributor

devos50 commented Oct 16, 2020

I think I found the issue! We are not sorting the elements based on the x-axis, see here.

I will fix this in #5626

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging a pull request may close this issue.

5 participants