|
|
|
|
|
by emn13
4854 days ago
|
|
There's no need to answer FUD with FUD: Firefox's UI does not become unresponsive with increasing number of tabs. Certainly not with just 50 anyhow; I do that all the time and never notice a slowdown. The tab-closing animation is less smooth than chrome's however. And while it's certainly true chrome uses more memory per tab, I can't imagine running into that problem very easily even on somewhat outdated hardware. A 4GB system should be able to do 50 tabs normally, and how much more do you need? |
|
I have noticed slowdown in Firefox's UI on both machines. More important than number of tabs, is CPU usage. For example my HTML5 heavy trading platform often causes the single-threaded Firefox UI to freeze and slowdown on both machines, while I have never noticed Chrome freezing when this site is open.
On the other hand, Chrome's UI runs smooth as butter until either open tabs or other programs bring memory usage to over 90% Physical Memory in the task manger. Recent builds hit that wall a lot quicker than it did a year or so ago.