Stories
Slash Boxes
Comments

SoylentNews is people

Firefox Nightlies: Electrolysis (Multi-Process) Now Enabled by Default

posted by LaminatorX on Friday November 14 2014, @11:59AM   Printer-friendly
from the separation-of-concerns dept.

gewg_ writes:

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

 
This discussion has been archived. No new comments can be posted.
Firefox Nightlies: Electrolysis (Multi-Process) Now Enabled by Default | Log In/Create an Account | Top | 41 comments | Search Discussion
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

  • (Score: 2) by mechanicjay on Friday November 14 2014, @02:28PM

    by mechanicjay (7) <{mechanicjay} {at} {soylentnews.org}> on Friday November 14 2014, @02:28PM (#115904) Homepage Journal

    Regarding memory usage and fragmentation -- I've seen things get much more stable with regards to Firefox and memory usage in the last year or so. I used to get tabs that leaked memory like crazy, to the point where if I left my browser open on my work machine over the weekend, I'd end up with a FF process using 4+GB of memory and be completely unresponsive. I haven't seen that behaviour in quite a while. Mostly my memory footprint stays around 1GB -- which is fine, I have a ton of tabs open on some heavyweight sites. Memory footprint itself doesn't bother me, as long as it's stable and not impacting the rest of the system.

    Regarding performance -- well, on anything older than a core2 Duo, I'm end up using Chrome, which is *noticeably* quicker to render pages on old hardware and keeps things usable. The only downside there, is that you're running Chrome.

    --
    My VMS box beat up your Windows box.
    Starting Score:    1  point
    Karma-Bonus Modifier   +1  
    Total Score:   2