Avatar for Username

Претражи подршку

Избегните преваре подршке. Никада од вас нећемо тражити да зовете или шаљете поруке на број или да делите личне податке. Пријавите сумњиве радње преко „Пријавите злоупотребу” опције.

Сазнај више

Ова тема је архивирана. Питајте друго питање ако вам је потребна помоћ.

High CPU usage when watching twitch

  • 2 одговорa
  • 1 има овај проблем
  • 2 прегледа
  • Последњи одговор послао Lorevyre

Lorevyre
Lorevyre
more options

I upgraded from windows 8 to windows 10 yesterday. When I was using windows 8 I had hardware acceleration turned off in firefox and chrome because having it on caused stuttering on twitch streams. But now with windows 10 if I don't have hardware acceleration turned on having FF or chrome open will use like 70% of my cpu when watching something on twitch. But if I turn it on it still causes the stutter.

With windows 8 with hardware acceleration turned off a twitch stream on source would use 30% cpu With windows 10 with hardware acceleration turned off it uses 70% cpu usage

I upgraded from windows 8 to windows 10 yesterday. When I was using windows 8 I had hardware acceleration turned off in firefox and chrome because having it on caused stuttering on twitch streams. But now with windows 10 if I don't have hardware acceleration turned on having FF or chrome open will use like 70% of my cpu when watching something on twitch. But if I turn it on it still causes the stutter. With windows 8 with hardware acceleration turned off a twitch stream on source would use 30% cpu With windows 10 with hardware acceleration turned off it uses 70% cpu usage

Сви одговори (2)

cor-el
cor-el
  • Moderator
  • Top 10 Contributor
more options

A forum search suggests that this happens because of Firefox using a lot of memory (2 GB or more).

What is the Firefox memory usage when this happens?

You can check the Firefox Task Manager (about:performance) and about:memory pages.

Lorevyre
Lorevyre Власник питања
more options

I reverted back to windows 8.1 and the problem still persisted. Oddly enough chrome stopped eating a lot of CPU when I reverted while firefox still is.