Changes

Jump to: navigation, search

Electrolysis

140 bytes removed, 11:19, 15 January 2015
summary updates
==Goal==
The goal of the current Electrolysis project ("e10s" for short) is to run render and execute web related content in a separate single background 'content' process from which communicates with the main Firefox itselfprocess via various [https://developer.mozilla.org/en-US/docs/IPDL ipdl protocols]. The two major advantages of this model are security and performance. Security would improve because the content processes could be sandboxed (although improvements are accomplished through sandboxing the content processes is a separate project from Electrolysis). Performance would improve because the browser UI would not be affected by poor , performance improvements are born out of content code (be it layout or JavaScript). Also, content the fact that multiple processes could be isolated from each other, which would have similar security and performance benefitsbetter leverage available client computing power.
Although the Gecko platform supports multiple processesFor current status, visit 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 current [[Electrolysis/Roadmap|project roadmapoverview]] has more details. The e10s team estimates e10s with a single content process will be enabled in Firefox Release by the end of 2015.
==Enabling and Disabling Electrolysis==
Confirm
1,982
edits

Navigation menu