Electrolysis (e10s) it is one of the core features of Firefox that Mozilla is currently working on. This feature or enhancement adds the much acclaimed multi-process architecture to Mozilla's browser.
The architecture multi-process, separates the open tabs from each other and the plugins on the other hand, strengthening not only the stability of the browser, but also its security. We should not confuse this with the "sandbox", but it is surely the gateway to making it a reality later.
Mozilla implemented Electrolysis in the channel versions Nightly de Firefox a few months ago in February. The implementation was experimental back then and disabled by default.
Tests showed that a lot of work needs to be done, especially regarding stability and compatibility with plugins. Work on Electrolysis has continued and there is, for now, a roadmap for planning the continuity of this feature until it is fully stable. This could vary according to the bumps that may appear during development.
Firefox multi-process, where and when?
Roadmap for multi-process Firefox architecture
- July 18th, 2014 - Milestone 1: make E10s usable for average Nightly version users but disabled by default.
- July 21th, 2014 - Firefox 34 development begins. Mozilla wants to use the next six weeks for Nightly channel users and plugin developers to test e10s and especially plugin compatibility.
- 1 for September, 2014 - Firefox 35 development begins. Mozilla plans to reach the second milestone in this development period. When milestone 2 is reached, Electrolysis is at a point where it can be enabled by default for users of the Nightly versions.
- 13 for October, 2014 - Firefox 36 development begins. This is the Firefox version, where the multi-process will be moved from channel to channel (Nightly> Aurora> Beta> Stable) until it is released in the stable version on February 16, 2015.
A change in the architecture is a major change and one of the consequences of the implementation of e10s, is that there are plugins that are not compatible with this.
Plugins that are not supported at the moment, among others, are Adblock Plus, LastPass, RequestPolicy, Greasemonkey, HTTPS Everywhere, BluHell Firewall or Video Download Helper.
Mozilla keeps track of plugin compatibility with e10s on the page Are We e10s yet. Here you can see the list of bugs, to see the progress of what is done to make this add-on compatible.
Many other popular add-ons have not been tested yet. Still, those that are constantly developed and updated will be corrected to make them compatible with e10s in case it was necessary. Other add-ons, on the other hand, those that are abandoned by their authors, will become defunct when e10s is part of the stable version of Firefox.
Source: FirefoxManía
Thank you very much for the info, it was something very necessary for Firefox. Just one question, on the dates you say, shouldn't it be 2015?
Not necessarily.
Currently the beta2 of Firefox32 is available, version 34 has been in development for not long, only they still do not make any alpha or beta available for download.
In other words, these are apparently the correct dates, only that some changes (or advances) are not visible to all interested parties, only to developers, testers or those registered in the development lists.
For July 2015 I do not think we are still going for version 34 or 35 of Firefox, rather we would go for 55 HAHA.
Don't tell me, because normally in Iceweasel, in the testing branch, it's just a headache to wait for it to be up to par with the current version of Firefox (it's horrible to have to wait for Iceweasel stable to catch up to Firefox ).
Anyway, I realize that Debian Wheezy supports Iceweasel better than Debian Jessie, which supposedly Iceweasel must be on the stable branch in your main repo.
And by the way, here's my tantrum in the forum.
Thanks for clarifying, I do not quite understand this accelerated development of Firefox
This feature is just great .. .. I look forward to it in the Nightly .. time flies by ..
Mish, Firefox à la Chrome for the multithreaded, it looks interesting. I just hope it doesn't consume a lot of RAM no more.
It would still be perfect if I used Webkit, that's why I prefer Chrome: 3
if i used webkit it would stop being firefox -.-
Exactly. That's why I won't use it, it doesn't even catch Blink 😀
Well, I still have to depend on Chrome for Motorola utilities 😀
Excellent news for Firefox and Iceweasel users.
And by the way, it's not that I have switched to Ubuntu or anything like that, it's that I got bored of waiting for Iceweasel on Debian Jessie to update to version 31.
Do not resist anymore and succumb to the charm of the ubuntera sect.
No thanks. I would like to go to Ubuntu, but with a slower APT than Debian, even some errors that can even be downloaded to the graphical server, I'd better go with Debian SID or Arch.
Ubuntu LTS? No thanks. With Debian Jessie I am more than satisfied.
Sent from my Debian Wheezy netbook with Iceweasel 31.
I had already told you that things happen to you that normal people don't ...
I've already tried Ubuntu LTS, but I don't like updates that force me to repair the video server.
And by the way, Firefox 31 runs the same as Iceweasel 31 (that is, fluid, although with a minor problem such as the cache inherited from Chrome, but the rest, great and with 15 open tabs and with an integrated reportbug that does not come in Iceweasel ).
Anyway, to deal with that kind of crash, I'd better go to Debian SID or Arch Linux 🙂
To alleviate the lack of multiprocessing, there is always the option of running firefox with the –no-remote parameter as follows:
/usr/lib64/firefox/firefox.sh -p –no-remote% u
this way multiple instances can be launched running separate processes
in my case I have created several launchers for each profile so that I can start them directly from the gnome panel.
I have for that ProfileSwitcher, which allows to open other profiles directly from the profile in which it is installed.
I love firefox the only thing I dislike is its compatibility with flash 🙁
I'm testing it and the difference is brutal…! it's very noticeable, especially when you load a lot of tabs at the same time. It is going to cost me a bit to return to the stable version, by the way, did someone notice the change in the configuration menu in the nightly?