[Amezarak]

While it would be nice for Firefox to have something in-place like per-process tabs that could mitigate the problem, I think what really needs to happen in this case is that they fix the underlying issue - which, true enough, might be a while; it doesn't happen for me, even though I leave Firefox open for about a month at a time (rebooting on patch Tuesday), so I assume it isn't easily reproducible and therefore might go some time without being fixed. Even if you had per-process tabs, I'd expect that one tab would still be using 30-50% of the CPU and thus be a major nuisance, even though it might make the rest of the browser more usable.

[lomnakkus]

It's completely trivial to write a "consumes-100%-CPU" JS script. I'm sure people usually don't do it intentionally, but I happened to encounter two such scripts on two separate domains today[1]. The surprising thing is Firefox managed to kill the first one, but not the second one -- after being completely unresponsive for 30s, mind you. It just hung when I pressed the "Stop script" (or whatever the button was labeled). Had to kill the whole FF process and restart it, being quick to close the two tabs that were causing trouble.

This is absurd. Apart from anything else FF needs to be better at protecting its users, and that includes separate-process-per-tab. (Ideally, it should be sandboxes, but honestly I'd settle for "separate processes" at this point in time.)

[1] One of them was http://www.xojane.com/