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

Clicking 'jump to first unread' froze Riot and caused it to consume 100% cpu #6548

Open
lampholder opened this issue Apr 17, 2018 · 3 comments
Labels
A-Timeline P2 S-Major Severely degrades major functionality or product features, with no satisfactory workaround T-Defect

Comments

@lampholder
Copy link
Member

From a rageshake.

@lampholder lampholder added T-Defect P2 S-Major Severely degrades major functionality or product features, with no satisfactory workaround A-Timeline labels Apr 24, 2018
@lampholder
Copy link
Member Author

P2 just 'cause we haven't seen lots of reports of this.

@ara4n
Copy link
Member

ara4n commented Sep 12, 2018

@uhoreg did you ever see this one again? i'm wondering if it was on an underpowered device that spent ages going through processing all the members from the /context request.

@uhoreg
Copy link
Member

uhoreg commented Sep 17, 2018

It was a somewhat-underpowered device, but not overly underpowered (~6 year old laptop)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-Timeline P2 S-Major Severely degrades major functionality or product features, with no satisfactory workaround T-Defect
Projects
None yet
Development

No branches or pull requests

3 participants