[anexprogrammer]

Ah, good, it's not just me!

One anecdote - 5 years ago FF was the clear winner for coping with tab abuse. Stable and coped with hundreds of tabs happily, Chrome started crashing pages beyond 50 or so.

Now it's the perfect reverse, FF hates a lot of tabs open and Chrome is stable with apparently limitless numbers.

[keeperofdakeys]

Personally I have both working fine with hundreds of tabs, but chrome uses 5-10 times the ram.

[anexprogrammer]

Hmm. Maybe it's a FF add-on causing the problems for me, though I'm not using anything uncommon. An internal ps like chrome has might help pinning that down.

Chrome is definitely the RAM greedy one (and so many processes!), and always has been.

[keeperofdakeys]

Firefox has "about:memory", which can give you some rather detailed information about memory usage.

[swatthatfly]

Chrome has chrome://memory-redirect/

[keeperofdakeys]

Strangely I can't find it in the latest dev release of chrome or chromium, it's still in stable. At least on linux, it also shows firefox's total memory usage, maybe they are doing lots of comparisons.

[basch]

firefox was stable but the chrome/ux hung if a tab hung. googlechrome was always responsive if a tab went berzerk.

[ngrilly]

Anybody knows what changed in Firefox?

[scholia]

Maybe the pages got bigger? On my Windows 7 PC, FF still handles a lot more tabs than Chrome, typically 2x or 3x as many.

Where Firefox falls over is with really heavy pages, such as infinite-scrolling image/gif sites. It's much better than it used to be, but it's still vulnerable.

With Chrome, pages fail to load (giving a blank page) and the Flash plug-in crashes. The browser does stay up, but the effect is the same: you have to restart it.