Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[Performance Issue] "Dark Reader is slowing down Firefox" on https://sqlitebrowser.org/stats/

See original GitHub issue

Performance Issue Report

Website Address

https://sqlitebrowser.org/stats/

Steps To Reproduce

Enable DR with Dynamic dark mode.
Go to https://sqlitebrowser.org/stats/
After a little while, get “Dark Reader is slowing down Firefox” message.
Also, notice that after doing the above, Firefox may take 5-30 seconds just to completely terminate it’s processes.

Performance Profile

No permission to upload.

System Information

OS: Windows
Browser: Firefox 95.0.0
Dark Reader Version: 4.9.43

Additional Context

Does this happen when Dark Reader is disabled? No.
Does this happen in other browsers? <smartass>No, other browsers don’t give a “Dark Reader is slowing down Firefox” message. 😃 😃 😃 Oh, okay, that’s not what you meant? 😃 </smartass>
Do you have hardware acceleration enabled? Hmmm… I do in the Firefox settings, but I don’t see it listed in about:support any more. Where can I confirm whether or not it is actually using hardware acceleration? gfx.webrender.all and gfx.webrender.software are both false, but those values appear to be the defaults.

Issue Analytics

State:
Created 2 years ago
Comments:6 (6 by maintainers)

Top GitHub Comments

2reactions

Gustedcommented, Dec 14, 2021

Which is the best way to fix this? Via a site-specific exception like #7630, or a global fix (if possible) to rectify the underlying cause of the performance issue (which will work on all sites)?

Every fix in the config is the best way to fix via the extension, yet this is a really deep issues in how sites behave. We had similar issues with “atlassian.net”, in a sense, we cannot store elements from the DOM, as they will updated and thus our version is a outdated one, nor do I want to add extra nonsense of attributes into the elements(causing other issues).

The issue is that certain elements on sites like these will go continue race between dark reader and the website to configure the element as they want(we want to modify it, the site wants to reset the element of our changes), given we cannot know if a element is in such loop, we cannot do a lot within the code to prevent this.

0reactions

Gitoffthelawncommented, Dec 15, 2021

Thank you for the great explanation. Makes perfect sense.