Closed
Bug 1355960
Opened 7 years ago
Closed 6 years ago
Riot.im burns large amounts of CPU in the background
Categories
(Web Compatibility :: Site Reports, defect, P3)
Web Compatibility
Site Reports
Tracking
(Performance Impact:?)
RESOLVED
INCOMPLETE
Performance Impact | ? |
People
(Reporter: heftig, Unassigned)
References
()
Details
Riot.im is a client for the Matrix network and one of the gateways to the Mozilla IRC network. Starting the release version https://riot.im/app/, switching it to a completely inactive room and letting it sit in a background tab averages about 37.5% CPU use (~9 min CPU time over ~24 min real time) and 1.6G RSS for the associated content process. The development version https://riot.im/develop/ is not noticeably different. I'm joined to about 65 rooms, some of them very large and very active. It would be great if a solution could be found to at least reduce background CPU usage. IMO the current situation is not acceptable for a chat application that needs to deliver notifications. Firefox 54.0a2, Arch Linux x86_64, Intel Core i7 6820HK
Comment 1•6 years ago
|
||
I'm not sure if this still reproduces, but perhaps someone from the qf team can take a looks.
Priority: -- → P3
Whiteboard: [qf]
Comment 2•6 years ago
|
||
Hi heftig, sorry it's taken so long, but is this still an issue? If so, could you try capturing a performance profile following these instructions: https://developer.mozilla.org/en-US/docs/Mozilla/Performance/Reporting_a_Performance_Problem
Flags: needinfo?(jan.steffens)
Reporter | ||
Comment 3•6 years ago
|
||
Because of the massive performance issue I've since reduced my use of Riot to a few small rooms. I'm not sure when and if I ever return to heavier usage. I will reopen the bug if I reencounter the problem.
Status: UNCONFIRMED → RESOLVED
Closed: 6 years ago
Flags: needinfo?(jan.steffens)
Resolution: --- → INCOMPLETE
Assignee | ||
Updated•5 years ago
|
Product: Tech Evangelism → Web Compatibility
Updated•2 years ago
|
Performance Impact: --- → ?
Whiteboard: [qf]
You need to log in
before you can comment on or make changes to this bug.
Description
•