Avatar for Username

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Èròjà atẹ̀lélànà yii ni a ti fi pamọ́ fọ́jọ́ pípẹ́. Jọ̀wọ́ béèrè ìbéèrè titun bí o bá nílò ìrànwọ́.

High CPU usage when watching twitch

  • 2 àwọn èsì
  • 1 ní ìṣòro yìí
  • 2 views
  • Èsì tí ó kẹ́hìn lọ́wọ́ 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

All Replies (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 Ìbéèrè olóhun
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.