Martin Brinkmann at gHacks reports
Electrolysis [(a.k.a. e10s a.k.a. multi-process Firefox)] has been in development for a long time but has been prioritized only recently by Mozilla (again) after not being in focus for some time.
[...]The core idea behind the new architecture is to separate web content from the core Firefox process. The two main advantages of doing so are security and performance.
Security benefits from potential sandboxing of web contents and separation of processes, and performance mainly from the browser UI not being affected by web contents.
[...]The Are We e10s yet website lists popular browser add-ons and whether or not they are compatible with e10s yet. If you browse the list of add-ons on that page you will notice that many add-ons are not yet compatible.
Mozilla made the decision to enable e10s for Firefox Nightly versions by default with [the November 7] update. This does not mean that the last phase of development has begun and that stable users will get the feature in three release cycles, however.
[...]users can disable e10s
(Score: 0) by Anonymous Coward on Friday November 14 2014, @05:47PM
You are doing it wrong.
I have a bunch of firefox profiles installed on Mint 16 they all have about 20 add-ons (noscript, adblock, requestpolicy, ghostery, https-everywhere, stylish, etc)
Currently running firefox 33.0, 64-bit.
With three separate instances (two different profiles) running for at least 2 days and each with at least 5 tabs in use (and 20+ tabs saved from the previous session but not yet reloaded) two are right around 390M resident, another is about 345M resident.
Also running a recent tor browser bundle and that's only 276M resident after 5+ days.