-
-
Notifications
You must be signed in to change notification settings - Fork 2
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
Issue: High CPU usage #27
Comments
I can get spikes up to
|
Thank you. I'll continue the stress tests to see what module is causing hiccups |
@Mishasama please try v5.33.4.8-beta to see if the Settings page has improvements on your system 😊 |
Indeed, this happens once these actions are active, even with the .8 version. And still get high usage on the stream page. Maybe... try asking ChatGPT to help with debugging? There are a few clues in my observations:
I found another issue. |
Stream page, yes, I want to start on the smaller, more manageable Setting spage first to see what can be changed.
|
Tabs consume about twice as much CPU when displayed in the foreground as when running in the background, so I suspect it's a rendering-related issue. Maybe you can reduce consumption by lowering the frame rate; there's a power-saving mode option in Chrome for lowering the frame rate globally, so maybe that helps somewhat? |
Those settings are managed by Chrome on the Application scale—I have little to no control over that. The best I can do is change how the extension works... |
Describe the bug
When opening and viewing the settings page, the CPU and memory usage is unusually high.
To Reproduce
Expected behavior
A settings page shouldn't have such a high CPU usage, is something caught in a dead loop?
Screenshots
Extension Information
5.33.4.6/7
store
&GitHub
chrome
&edge
Windows
Additional comments
CPU usage drops to single digits when placing the page in the background without displaying it, is this caused by any active element rendering over and over again?
Also, when using TTVT, all Twitch tabs' CPU usage goes high.
From Ephellon
100ms
The text was updated successfully, but these errors were encountered: