-
Notifications
You must be signed in to change notification settings - Fork 413
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
[Bug]: App starts to lag when I select a playlist with alot of songs #2050
Comments
Can you reproduce this issue on the website https://music.youtube.com using a chromium based browser? (e.g. chrome, Vivaldi, opera, Microsoft edge) |
I'm using the app....also the lag isn't present on the browser. |
I think that's obvious.
Great, that's what I wanted to confirm |
What should I do now...? |
Same here, when I select the "My Supermix" playlist the playlist overview page becomes super laggy. Noticed 2 of my CPU cores spike to 100% usage when scrolling. GPU seems to do nothing at 0% usage. Does not happen on Chrome, music.youtube.com website. |
Also have this issue after updating from 3.3.6 (where adblocker stopped working) to 3.3.9. Looks like hardware acceleration is being disabled regardless of the corresponding setting. |
I noticed that turning off In-App Menu fixes the problem. 3080 Ti; R9 5950X; 32GB RAM; should not have any issues |
Yep this fixed it for me too |
Seems to have fixed it here as well. |
Preflight Checklist
YouTube Music (Application) Version
3.3.6.0
Checklists
What operating system are you using?
Windows
Operating System Version
Window 11 Home
What CPU architecture are you using?
x64
Last Known Working YouTube Music (Application) version
No response
Reproduction steps
Select a playlist with alot of songs.
Expected Behavior
App stays fluid and no lag.
Actual Behavior
App immediately begins lagging and song selecting/scrolling has a huge delay until choosing a playlist with significantly less songs.
Enabled plugins
Exponential Volume
In-App Menu
Additional Information
No response
The text was updated successfully, but these errors were encountered: