I was wondering about the benefits of this. Supposedly having tabs in different processes should improve performance of the browser in general, as slow running scripts in one tab process won't slow down the main UI process. I have come across this problem before, including the whole browser freezing from some slow JS. But does this need to be done with separate processes? Surely running tabs in a different thread to the UI should solve this issue too?
I'm a bit concerned about the effect this could have on RAM usage and plugin compatibility - the linked wiki page already lists two plugins that I can't live without (NoScript and Tree Style Tabs) as being incompatible. Hopefully that will be fixed before this becomes default in a release.
Part of it is probably that browsers use so much shared global data that it is easier to just make another process. There are also fault isolation and security benefits you get from splitting the web content into a process that can have a tighter sandbox policy.
I'm a bit concerned about the effect this could have on RAM usage and plugin compatibility - the linked wiki page already lists two plugins that I can't live without (NoScript and Tree Style Tabs) as being incompatible. Hopefully that will be fixed before this becomes default in a release.