Although the Gecko platform supports multiple processes, the Firefox frontend is not designed to use them. Work to make the frontend (including addons) support multiple processes was begun in early 2013. The project roadmap has more details.
We're developing off of mozilla-central. Therefore, it's possible to enable Electrolysis right now in Firefox nightlies.
- Update to a current nightly.
- We strongly recommend you create a new profile!
- Set the browser.tabs.remote preference to true.
- As of Firefox 30 set browser.tabs.remote.autostart to true to always enable e10s; otherwise, create a new e10s window.
- Restart Firefox.
What to Expect
Basic browsing should work as expected. Tabs that are loaded remotely (i.e., in a separate process) will have their title underlined. By default, only one content process is used. You can control this with the dom.ipc.processCount preference.
- Back and forward buttons
- URL bar and search bar
- Context menu (somewhat)
- Middle clicking to open links
- Flash (sometimes)
- Add-on installation on a.m.o (without download progress)
- The find bar
- Session restore
What doesn't work yet:
- Developer tools
- Many addons
- Many plugins
- Click to play
Most bugs in electrolysis occur because code in the chrome process tries to access data in a content process. All of the DOM objects for a XUL browser element, as well as its DocShell, live in the content process. Typical access paths are via
browser.docShell, or some variation of them. Often, these property accesses will generate errors in the console, which makes these bugs fairly easy to detect.
The ideal way to solve these problems is with the message manager. Any code that touches data in the content process should run in a content script. Content scripts communicate with chrome by message passing. Often, it's fairly easy to partition code into content and chrome portions and use message passing to communicate.
However, there are cases where it is awkward to partition code in this way. In these cases, it may be beneficial to use cross-process object wrappers (CPOWs). CPOWs make it easy to transparently access content objects from chrome. The main drawback of CPOWs is that they are slow and they cause the chrome process to block, which can lead to jank. However, there are times when it makes sense to use CPOWs. For example, CPOWs are used to generate the menu items for the Firefox context menu. Creating the context menu sends a small number of CPOW messages since it doesn't touch the content document very much. And while the main event loop will be blocked while generating the context menu, users are unlikely to notice since they're just waiting for the menu to appear.
|Weekly Team Meeting||Thursday at 2:30pm PT (5:30pm ET) for 30 mins|
|High Level Oversight||
Here is what the letters following each name stand for, those higher on the list include all those below:
- R = Responsible for deliverable, in most cases this is anyone writing code.
- A = Accountable for the final decision making on some aspect of the project, often leadership that is not working on code but have go, no go decision making.
- C = Needs to be consulted on key topics, often this would be for subject mater experts that need to be consulted but don't have decision making power.
- I = Needs to be kept informed, those that just need regular status reports sent to them.
- Tim Taubert's "Firefox Electrolysis 101" blog post (2011)
- For latest meeting notes, see the Meeting Notes Etherpad.
Create a new weekly agenda from the template: