SoylentNews is people
SoylentNews
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: 2) by Marand on Saturday November 15 2014, @04:21AM
I just did a clean installation of Firefox 33.1 on a fresh Ubuntu 14.10 VM. After starting it up, and after it has loaded its default page, it's using 527 MB of real memory. 499 MB is private.
I'm looking at 326 tabs, 525mb used. Debian, 32bit+PAE, iceweasel 31.1. RAM use without tabs was something like 250mb last I checked. Most of the memory use ends up being from javascript, so NoScript helps a lot.