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

App becomes very laggy after more than 30 mins of continous playing? #797

Closed
Shnxxx opened this issue Aug 20, 2022 · 3 comments
Closed

App becomes very laggy after more than 30 mins of continous playing? #797

Shnxxx opened this issue Aug 20, 2022 · 3 comments
Labels
fix-available A fix to the issue is available in a new version

Comments

@Shnxxx
Copy link

Shnxxx commented Aug 20, 2022

I always listen to music on this app, and I usually play it through my speakers so I can hear it wherever I go in our house. After about 30 minutes of continuous play, it takes too long to respond and is very laggy.

@kerichdev
Copy link
Contributor

Can +1 this one, although it may be related to a memory leak issue in Youtube Music itself (has been once discussed on the subreddit, confirmed by various users)

@sh0inx
Copy link

sh0inx commented Sep 4, 2022

+1, what thread is that on? I'd like to take a look and see, as I switched from a different client to this one because of the same issue (this one is better, if you're wondering)

@MulverineX
Copy link
Contributor

MulverineX commented Sep 12, 2022

@sh0inx well if its an issue with the web app itself; not this electron wrapper/mod (which is probably the case according to kerich), then there's not much that can really be done without complex analysis & patching of the JS bundle or a full web replacement. Currently, this mod works with raw DOM manipulation and JQuery (😬), so doing modifications like this isn't really feasible.

Perhaps a system to detect when memory usage gets that high and refreshes the next time the track changes (so it doesn't interrupt playback). Could have an option in the dropdown menu to set the current usage as "too much" and have it remember thats where you want it to refresh. If refreshing doesn't free the memory then restart the app. That'd be a decent solution.

@JellyBrick JellyBrick added the fix-available A fix to the issue is available in a new version label Oct 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
fix-available A fix to the issue is available in a new version
Projects
None yet
Development

No branches or pull requests

5 participants