[jjoonathan]

If process isolation is indirectly responsible for the "page freezes, doesn't re-render, doesn't respond to input" symptom then it seems to have cost more than it was worth in the stability department. Those freezes have dogged chrome on both my mac and my pc for the last 4 or 5 years every time I've tried it. Safari and firefox, OTOH, almost never seem to crash or become unresponsive.

I'm all for having clever damage control mechanisms, but having less damage in the first place seems to be the winning strategy.

[krakensden]

Process isolation isn't actually on yet, it's still opt-in in Aurora.

It also makes everything about the interactive experience worse, or at least it did last week. `perf top` shows a pretty damning story around locks, too. So- we're probably not going to see it until 2015.

[jjoonathan]

I wasn't complaining about lack of process isolation in firefox, I was complaining that process isolation in chrome caused more trouble than it was worth.

FWIW After re-reading my post I believe your mistaken impression was due to lack of clarity on my part, not laziness on your part.

[comex]

Note that Safari also uses out-of-process rendering (using WebKit2).

[jjoonathan]

Well, I guess Chrome's implementation just sucks then. ¯\_(ツ)_/¯