Jump to content

Mozilla plans to release Electrolysis (multi-process architecture) with Firefox 36


rach

Recommended Posts

Electrolysis (e10s) is one of the core improvements for Firefox that Mozilla is currently working on. The feature adds so-called multi-process support to Firefox in a way similar to how Chromium-based browsers make use of it already.

A multi-process architecture that separates the browser's core from open websites and plugin contents improves not only the stability of the browser but also the security of it.

This should not be confused with sandboxing though even though Electrolysis is the gateway to make that happen later on.
Mozilla implemented Electrolysis in Nightly channel versions of the Firefox web browser back in February. The implementation was experimental back then and disabled by default.

Tests showed that work needed to be done, especially in regards to stability but also compatibility with add-ons.

Work has continued on Electrolysis and a roadmap was released recently by Mozilla developer Chris Peterson which puts Mozilla's current development and launch plans in regards to the feature on paper.

It needs to be noted that the roadmap is not set in stone and that bumps in the road may delay the project.

firefox-oop-window.png


Firefox Multi-process architecture roadmap

  • July 18, 2014 - Milestone 1: make E10s usable for average Nightly users but is not enabled by default.
  • July 21, 2014 - Firefox 34 development begins. Mozilla wants to use the six weeks that follow to get Nightly users and add-on developers to test e10s and especially add-on compatibility.
  • September 1, 2014 - Firefox 35 development begins. Mozilla plans to reach Milestone 2 in this development period. When Milestone 2 is reached, Electrolysis is at a point where it can be enabled for Nightly users.
  • October 13, 2014 - Firefox 36 development begins. This is the version of the browser where Firefox's multi-process architecture will be moved from channel to channel (Nightly > Aurora > Beta > Stable) so that it is released to the stable channel of the browser on February 16, 2015.

Add-on compatibility

A change in architecture is a major change and one of the consequences of implementing e10s is that there are add-ons that are not compatible with it.

Add-ons that are not compatible right now are among others Adblock Plus, LastPass, RequestPolicy, Greasemonkey, HTTPS Everywhere, BluHell Firewall or Video Download Helper.

Mozilla keeps track of add-on compatibility with e10s on the Are We e10s yet page. Here you find bugs listed that you can follow to find out if progress is being made to make the linked add-on compatible.

Many popular add-ons have not been tested yet, with the page only listing some of them.

Still, it is very likely that most add-ons that are still actively developed will continue to work as developers will fix them to make them compatible with e10s.

Other add-ons, those abandoned by their authors on the other hand may become defunct when e10s gets released to Firefox Stable.

:view: View: Original Article

Link to comment
Share on other sites


  • Replies 14
  • Views 2.7k
  • Created
  • Last Reply

Top Posters In This Topic

  • dcs18

    3

  • truemate

    3

  • CODYQX4

    2

  • rudrax

    2

Its already enabled in 33.0a1 and under file you can use New e10s Window.

Edited by RobrPatty
Link to comment
Share on other sites


Add-on compatibility

A change in architecture is a major change and one of the consequences of implementing e10s is that there are add-ons that are not compatible with it.

Add-ons that are not compatible right now are among others Adblock Plus, LastPass, RequestPolicy, Greasemonkey, HTTPS Everywhere, BluHell Firewall or Video Download Helper.

Add-ons compatibility is a negligible niggle - their Authors, I am confident will get the necessary upgrades done, on time.

Link to comment
Share on other sites


first make firefox to work perfectly with adobe/flash...its struggling with flash.

eats bloody lots of memory when on youtube

Link to comment
Share on other sites


Very slow progress towards introducing Electrolysis.

Link to comment
Share on other sites


first make firefox to work perfectly with adobe/flash...its struggling with flash.

eats bloody lots of memory when on youtube

No such issue observed, here. :uhuh:

Link to comment
Share on other sites


first make firefox to work perfectly with adobe/flash...its struggling with flash.

eats bloody lots of memory when on youtube

No such issue observed, here. :uhuh:

but its happening here from past thru v20's

not talking abt waterfox

Link to comment
Share on other sites


first make firefox to work perfectly with adobe/flash...its struggling with flash.

eats bloody lots of memory when on youtube

No such issue observed, here. :uhuh:

but its happening here from past thru v20's

not talking abt waterfox

I am not referring to Waterfox, either.

Link to comment
Share on other sites


Purple Trail

first make firefox to work perfectly with adobe/flash...its struggling with flash.

eats bloody lots of memory when on youtube

Uninstall the crappy flash player, YouTube and most sites work without it, thanks to html5. It's less CPU intensive and resource hungry, plus you get more battery life if you're on a laptop. If you really stumble upon a video that needs flash, just open it in Chrome or any other browser that has flash player integrated.

The future is plugin free.

Edited by Purple Trail
Link to comment
Share on other sites


first make firefox to work perfectly with adobe/flash...its struggling with flash.

eats bloody lots of memory when on youtube

Uninstall the crappy flash player, YouTube and most sites work without it, thanks to html5. It's less CPU intensive and resource hungry, plus you get more battery life if you're on a laptop. If you really stumble upon a video that needs flash, just open it in Chrome or any other browser that has flash player integrated.

The future is plugin free.

U right,in between i try to disbale flash for firefox,,and checked the performance of it...really FF worked fine withour flash..or else it was on knees after an hr use of any flash related site.

and again u right,,as i already start using IE11 or chrome for flash and they working like a charm for ctnd use without any prob.

SO A BIG NOOO FOR FLASH RELATED SITE (YOUTUBE OR ANY OTHER TUBE SITE) in FireFox.

But those html5 wont support all videos in youtube & i think therez nothing like 480p view for it :-/ as i mostly watch youtube vids in that resolution.

Hope in comeing future,,,there would be end for this FLASH ... plugins and less resource eater html5 become more advance :)

Edited by truemate
Link to comment
Share on other sites


Purple Trail
But those html5 wont support all videos in youtube & i think therez nothing like 480p view for it :-/ as i mostly watch youtube vids in that resolution.

Hope in comeing future,,,there would be end for this FLASH ... plugins and less resource eater html5 become more advance

In the advanced settings page (about:config) you can set media.mediasource.enabled to true. This setting will enable MSE and give you the option to view content in 480p and the rest of the resolutions. You should be aware that this is still experimental, so it might not work as expected for now.

I suggest you update to Firefox 32 Beta. http://www.nsanedown.com/?news=245440701

How to enable Media Source Extensions in Firefox - http://www.ghacks.net/2014/05/10/enable-media-source-extensions-firefox/

with media.mediasource disabled with media.mediasource enabled

KCuYycz.pngtZAHarW.png

Edited by Purple Trail
Link to comment
Share on other sites


I hope, this implementation will reduce the CPU usage too.

Link to comment
Share on other sites


  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...