After years of development and several delays, multi-process Firefox, also known as Electrolysis or e10S, is about to be enabled for a subset of Firefox stable users.
The following guide provides you with information about Firefox's multi-process architecture. It explains what the feature offers, preferences and switches for it, covers add-on compatibility, and takes a look at the future of the feature.
Mozilla plans to enable the multi-process architecture for a subset of Firefox Stable users when the browser reaches version 48. If things go as planned, Firefox 48 will be released on August 2, 2016.
The multi-process rollout has started, and is ongoing (as of Firefox 52). Mozilla plans to increase the number of content processes to four for the stable population in Firefox 54.
Electrolysis functionality hosts, renders, or executes web related content in background child processes which communicate with the "parent" Firefox browser via various ipdl protocols.
The Multi-process architecture improves the browser's stability, performance and security by separating tasks into processes.
The first iteration of multi-process Firefox moves NPAPI plugins, media playback and web content to child processes thus separating them from the browser's core.
The easiest way to find out whether multi-process Firefox is enabled is the following one:
It should read enabled or disabled, and gives you a direct answer about the state of multi-process functionality in the browser.
If multi-process support is not enabled yet in Firefox, you may enable it manually. This is true even if you run Firefox 47 Stable as the functionality is already there.
Before you do so, you may want to run compatibility checks for add-ons though. If you don't run add-ons, about 40% of Firefox users don't according to Mozilla, you may skip the step.
While you can jump into water right away by enabling Electrolysis without verifying compatibility first, it is highly suggested to verify that all important add-ons are compatible with e10s before you do so.
You may check out the Are We e10S Yet site which lists top add-ons and their compatibility with e10s. The majority of Firefox add-ons are not tested though so that you may be none the wiser after checking your add-ons on the site.
What you can do, is create a secondary profile in Firefox, copy all extensions of the first profile to it, and enable e10s for that secondary profile.
This is far from ideal though. An alternative is to disable all add-ons, enable e10s, and enable extensions one by one to find out whether they are compatible.
To enable or disable multi-process Firefox, do the following
Setting the value of browser.tabs.remote.autostart to true enables the multi-process architecture in Firefox, setting it to false disables it.
Please note that you need to restart the browser when you change the preference's value.
Some configurations, if accessibility is used or add-ons are incompatibility, prevent Electrolysis from being enabled.
The about:support page mentioned previously list the reason so that you know why multi-process is not working.
You may force-enable multi-process functionality in Firefox. I recommend that you backup your user profile before you do.
Note that forcing compatibility may have a big impact on performance if add-ons are incompatible with e10s.
There is another preference that you may need to change on about:config.
This prevents the blocking of multiple content processes by add-ons.
Mozilla Firefox uses one content process by default right now when multi-process Firefox is enabled. Mozilla plans to change that in Firefox 54 by increasing the number of content processes to 4 in that version.
You can modify the count right now, to raise or decrease the limit. Note that Firefox will ship with an option in the browser's settings eventually that lets you do that.
You can check the about:support page in Firefox to find out whether multi-process is enabled or not.
You will notice several firefox.exe processes when you run a process manager, e.g. the Windows Task Manager which highlights that Electrolysis is enabled.
Firefox should for the most part run just like before. Ideally, enabling multi-process functionality should improve the browser's performance and stability right away.
You may however notice a higher than usual RAM usage. Mozilla confirmed that Firefox with Electrolysis will use about 20% more RAM.
Mozilla will continue to work on multi-process Firefox after the initial roll out of the feature. The organization plans to bring sandboxing to Firefox which, on Windows, is based on the Chromium sandbox that Google uses in Chrome. This sandbox will improve security significantly when enabled.
Now You: What's your take on the coming roll out of e10s in Firefox?
Advertising revenue is falling fast across the Internet, and independently-run sites like Ghacks are hit hardest by it. The advertising model in its current form is coming to an end, and we have to find other ways to continue operating this site.
We are committed to keeping our content free and independent, which means no paywalls, no sponsored posts, no annoying ad formats or subscription fees.
If you like our content, and would like to help, please consider making a contribution:
Ghacks is a technology news blog that was founded in 2005 by Martin Brinkmann. It has since then become one of the most popular tech news sites on the Internet with five authors and regular contributions from freelance writers.