Electrolysis will initially only have two processes: one for chrome (i.e. UI) and one for web content. More content processes may be used in the future, but we will move very slowly and carefully in that direction. I consider the several-hundred-tabs-open use case to be an important one, and will do my best to ensure it continues to work in the future.

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.

Chrome doesn't isolate misbehaving webpages. The pages are grouped together under a few parent processes. The more pages you have open, the larger the group and a page crash will take out many more pages at the same time.

Originally the idea was for every page to be isolated but that didn't scale so well.

I haven't followed (and probably don't know nearly enough anyway) details of e10s, but their claim is contrary to your view:

> 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.

https://wiki.mozilla.org/Electrolysis#Goal