NaturalViolence Wrote:Whereas FF seems to just stop whatever tab/plugin is causing the problem.Chrome do this, however, it "wait" a plugin response more than Firefox.
About memory usage, Chrome uses less memory than Firefox, even with many tabs. What makes chrome slow with multiple tabs is the sandboxed plugin system: for every new tab, a new "thread" (or something like that) are opened for every plugin running at the moment. Test opening 100+ Google pages (google.com) on Firefox and Chrome, then go to Taks Manager: Chrome will be using about 50-200MB less memory. It's negligible, but the difference is there.
However, just install a lot of extensions and plugins on Chrome and all speed advantages it have over Firefox are gone: even the cold statup times get slower compared to Firefox with lots of extensions...
After all, there isn't "The best browser". It's a personal choice, people should use the browser that he/she likes. For a long time, IE7 was the best browser for me (YES, IE7!). After some releases, Chrome became the best in my opinion, and I'm using it right now...
And for the ones discussing about what browser starts quickly, test IE9 (Vista, 7, 8) or IE10 (Windows 8 only). It'll start even faster than a fresh install of Chrome...
Avell A70 MOB: Core i7-11800H, GeForce RTX 3060, 32 GB DDR4-3200, Windows 11 (Insider Preview)
ASRock Z97M OC Formula: Pentium G3258, GeForce GT 440, 16 GB DDR3-1600, Windows 10 (22H2)
ASRock Z97M OC Formula: Pentium G3258, GeForce GT 440, 16 GB DDR3-1600, Windows 10 (22H2)