Firefox vs Chrome Tabs

Chrome does, Firefox does not (I've got 5 processes for a billion tabs.)

I have 1450 tabs open and Firefox is fine, Chrome would be an unusable mess.

I usually have a few hundred tabs open in Firefox without issue; it seems to do a good job of putting unused/old tabs to 'sleep' until you come back to them.

Try to open 100 tabs, first in Chrome, then in Firefox. Chrome doesn't even show the titles and runs quickly out of memory.Chrome's process model incurs in substantial overhead, opening tens of tabs in a low-spec PC it's a surefire way to freeze the system.

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

751 tabs open right now and growing.Firefox copes fine. Me? Not so much (:

My firefox browsing way is to open every link in new tab. Going back and forth in same tab caches every page browsed in the tab so it increases memory consumption. In this I usually end up opening 40+ tabs. But tab management is super easy with firefox thanks to tree style tab extension. Even 40+ tabs opened my firefox memory consumption is much less than chrome opened 40+ tab (which is unmanageble due to shrinked size of tab bar)

My tabs have gotten out of control (they are in the hundreds (due to reasons)), but Firefox handles it quite nice. It only gets restarted after updates, so they are long-lived as well.Chrome seem to struggle when there are tens of tabs.

This does not happen to me on Firefox, I am running 2 windows with dozen tabs each.

I've noticed that I can have a hundred tabs open in Firefox without much damage, but if I open a hundred tabs in Chrome, my CPU starts to run full-blast making the machine impossible to use.