I don't remember when this has last happened to me. If this is the major reason, I, most definitely, prefer the current Firefox approach: much less memory utilization and the chance that I have to restart the browser once in a blue moon (not a problem for me in real use) vs very high memory usage but I'm protected in the off chance that one tab messes up my browser (and I always have to live with the high memory usage).

So FF devs, if you're listening, this is a vote against Electrolysis (if it means higher memory usage than current FF).

I seem to run into that pretty frequently on Firefox 19 at work, but I don't think I ever notice it when I'm running 23 at home.

I've been on the Aurora channel for some time now and it's been a pretty smooth ride for me. You should give it a try to see how it works out for you.

I still can't understand how a freezing js could stop browser, can't they handle that stuff on a different thread other than browser's main ui thread?

With plugins already in a different process, these situations are far less likely.

But you only get 15 tabs.