darkreader / darkreader/darkreader
[Performance Issue] Wezterm wiki slowdown on both firefox and chromium-based browsers
- Dominant language
- TypeScript
- Stars
- 22.4k
- Forks
- 2.7k
- Avg merge
- 21h 11m
- Merged PRs (30d)
- 78
Description
### Prerequisites
- [x] I [searched for any existing report](https://github.com/darkreader/darkreader/issues?q=is%3Aissue) about this performance issue to avoid opening a duplicate.
- [x] I have restarted the web browser to check if that resolved this performance issue.
- [x] I can reproduce this performance issue in a new, unmodified web browser profile with Dark Reader installed as the only extension.
### Performance Issue Description
Across the wezterm wiki
Testing on Arch Linux in latest Vivaldi, this jumps memory usage by about 1 GB when opening the page, in one instance jumped from 8 GB to 12 GB(!) then 9.5 GB memory usage with CPU fans ramping up, this did not happen consistently however.
But, it consistently causes severe, website-breaking performance issues across the wezterm wiki on both browser platforms
The page completely froze multiple times while recording the linked performance profile; it popped up the banner that DarkReader is slowing down the browser (stop/debug buttons) 3 separate times
### Website Address
https://wezterm.org/config/lua/keyassignment/index.html
### Steps To Reproduce
1. open wezterm wiki (config sections)
2. disable website dark mode, which I don't think was on by default? on the navbar, so it shows a sun, not a moon
3. browse / force refresh page with Ctrl+F5 / etc.
### Performance Profile
https://share.firefox.dev/44TAjsG
### Screenshots
_No response_
### Operating System
Arch Linux 6.15.8-arch1-1
### Web Browser name and version
Librewolf 141.0-1; Vivaldi 7.5.3735.56 (Stable channel) stable (64-bit)
### Dark Reader version
4.9.110
### Does this happen when Dark Reader is disabled?
No
### Does this happen in other web browsers?
Yes
### Additional Context
_No response_
Contributor guide
Assessment
This issue has not been assessed yet.