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

Riot app unusably slow with Firefox (or Waterfox) in safe mode #5894

Closed
grahamperrin opened this issue Dec 28, 2017 · 2 comments
Closed

Riot app unusably slow with Firefox (or Waterfox) in safe mode #5894

grahamperrin opened this issue Dec 28, 2017 · 2 comments
Labels
A-Performance P3 S-Minor Impairs non-critical functionality or suitable workarounds exist Z-Platform-Specific

Comments

@grahamperrin
Copy link

Description

Whilst attempting to troubleshoot a different issue, I attempted to use Riot with Firefox in safe mode. I discovered that the app is unusable with the browser in that mode.

Steps to reproduce

On a relatively old, slow machine (Ergo Vista 621, 4 GB memory) with Firefox 57.0.1 (64-bit) on Kubuntu:

  • Riot never becomes usable.

On a relatively modern, fast machine (HP EliteBook 8570p with 16 GB memory) with Waterfox 56.0.1 and Firefox 56.0.2 (64-bit) on FreeBSD-CURRENT:

  • after an extraordinarily long wait, Riot might load but periods of usability (interspersed with long periods of the app not responding) seem to last no longer than a second or two

– and if multiprocess is disabled (e.g. browser.tabs.remote.force-disable) then the entire browser is non-responsive for terribly long periods. Yesterday, for example:

Firefox 56.0.2 … just responded, momentarily, after around twenty-two minutes.

Logs can not be sent, because the application is unusable.

@lampholder
Copy link
Member

Clicking the Start in Safe Mode button will temporarily disable your extensions and themes, turn off hardware acceleration and reset toolbar and button customizations. When you leave Safe Mode and start Firefox up normally, your extensions, themes, and settings will return to the state they were in before you entered Safe Mode.

I would guess that safe mode might hide state in localstorage/indexeddb forcing a full resync. Coupled with the lack of hardware accelleration maybe, plus general worse performance on FF (still), this might be causing this problem.

@t3chguy
Copy link
Member

t3chguy commented Nov 14, 2024

Closing this as presumed fixed in the many years due to lack of further reported cases

@t3chguy t3chguy closed this as completed Nov 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-Performance P3 S-Minor Impairs non-critical functionality or suitable workarounds exist Z-Platform-Specific
Projects
None yet
Development

No branches or pull requests

3 participants