The response is standard too... Electrolysis. Wait for it.
If I could only choose one I'd choose the browser that isolates misbehaving web pages but both is even better.
I personally think the number of browser processes shouldn't exceed the number of tabs because you won't get any responsiveness improvements beyond that, and it'll keep the memory usage reasonably low.
Originally the idea was for every page to be isolated but that didn't scale so well.
Electrolysis will help with some performance problems, but not all.
It will fix the crashing tab equals crashing browser issue, but that is a very different problem.
> Performance would improve because the browser UI would not be affected by poor performance of content code (be it layout or JavaScript). Also, content processes could be isolated from each other, which would have similar security and performance benefits.
Having said that, if someone is experiencing bad performance and they do have extensions enabled, temporarily disabling them is a good diagnostic step. If performance improves, it's clear that it's an extension at fault, and then bisection can be used to work out which one. Otherwise, it's clearly a Firefox problem and a bug report (bugzilla.mozilla.org) would be very helpful!
Chrome on the other side, starts degrading my entire system's performance forcing it to hit swap memory the second the string of tabs on my top bar threatens to stretch across the screen. No need to wait for 'months of use without closing'...