4 ms·

I welcome this just so we can determine which tabs are using the CPU persistently. I had to switch back to Chromium (after a good few weeks really giving FF ano

by nly 13y ago

I welcome this just so we can determine which tabs are using the CPU persistently. I had to switch back to Chromium (after a good few weeks really giving FF another go) because I was sick of this issue. Firefox is smoother and more memory friendly than Chromium these days, a pleasure to use, but in Chrome I can kill hoggy tabs... so that's where I'm staying for the moment.

girvo 13y ago
Now, this isn't snarky, but you really run into issues like that, where its noticeably bad in a particular tab, enough to need to kill it? What sort of sites, and what processor?
- nly 13y ago
  In Chromium it's generally runaway memory hogging tabs. Facebook is generally awful for example. Leave any Facebook page open all day (background of course, possibly on another virtual desktop) and you'll be staring at a multi-GB tab by evening. I'm not sure what's causing the CPU utilisation in Firefox. It's common to blame extensions in the FF community because there's no easy way to determine where the problem is.
- andor 13y ago
  Every other day I hit the problem that a tab consumes so much CPU that it stutters. After closing that tab and reopening the same web site the issue is gone. That's using Chrome stable both on Linux and Android.