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

High cpu usage, sometimes GPU usage. #11

Open
PauldeKoning opened this issue Oct 1, 2019 · 8 comments
Open

High cpu usage, sometimes GPU usage. #11

PauldeKoning opened this issue Oct 1, 2019 · 8 comments

Comments

@PauldeKoning
Copy link

I am getting relatively very high cpu usage (10-20%) even when the program is idle and not playing music. Furthermore it's sometimes using my dedicated GPU for 5-10% which it shouldn't do in any case I believe.

I have an i5 6600k and a rx vega 56.

@lakimens
Copy link

lakimens commented Nov 5, 2019

I came to post this. I usually run DOTA 2 at around 100FPS on a 120Hz monitor so it's noticeable when I have lower FPS. I had this running in the background and it froze multiple times.

When I turned it off, my FPS probably doubled - not even joking. Extremely heavy on the CPU and possibly memory. Using the browser is much more efficient.

@MaverickMartyn
Copy link
Owner

I've seen those issues myself. This shouldn't be an issue in my rewrite. Sorry about the long delay on that.
I suspect I may have a memory leak somewhere obscure.
I expect to be back on this project in the near future.

@brittenr
Copy link

Hi Martyn, I also experienced this problem recently - even just after loading the app i experienced ~3% gpu usage

@kameryn1811
Copy link

Dang, same here.

I love this app, but I've stopped using it for now. I do a lot of animation and compositing, and my computer locks up regularly if I have it open, once I discovered it was the culprit and closed it, no issues.

Note: the same thing happens if I open the official Youtube Music website in chrome, so not sure it's the app that's the issue. But if you have any way of restraining Youtube music that'd be amazing.

Looking forward to this getting fixed.

@PauldeKoning
Copy link
Author

PauldeKoning commented Jan 5, 2021 via email

@brittenr
Copy link

brittenr commented Jan 5, 2021

Following on from your point Paul, I don't observe this behaviour when using YTM on firefox

@Hi-Angel
Copy link

Hi-Angel commented Oct 23, 2022

Since the problem persists on a browser as well, I collected some observations, hopefully they will be useful:

  • --no-sandbox fixes it for Chrome
  • The problem may happen in both Chrome and Firefox, however on Firefox it happens sporadically, whereas in Chrome it's always reproducible
    • in Firefox the problem may appear at first, but then go away. From what I've seen it never reappeared again unless I restarted Firefox. Closing/Opening the tab in particular never made it start reproducing again for me.
  • Problem never appears in Chrome nor Firefox if you are logged out. IOW it is only reproducible when you're logged-in.
  • CPU usage is a little bit higher in Chrome (≈22%), than it is in Firefox (≈16)
  • In both browsers the process has lots of threads — graphics stuff, audio, media… However, the CPU is always being taken by the main thread whose TID is equal to the PID.
  • it's caused by various timeouts
    • Chrome repeatedly calls a futex() and gets a "Connection timed out"
    • Firefox repeatedly calls a poll() on read-side of a pipe, but receives TIMEOUT

@Hi-Angel
Copy link

Found a workaround for Chrome: running it with --no-sandbox makes problem disappear.

Couldn't find something similar for Firefox, because I no longer can reproduce it there.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants