Mozilla's list of e10s-compatible add-ons showed just 8 of the top 20 Firefox extensions: Notable conflicts included FireBug and NoScript Security Suite. That half, Mozilla has determined, were the best candidates because they didn't rely on add-ons, the biggest stumbling block to e10s.īecause the aged extension model assumed that the browser and content used the same memory space, existing add-ons must be modified. At this point, only about 1% of roughly half of the user base has been given the multi-process version of Firefox 48.
After taking a pause of several years, engineers resumed work in mid-2015.Īs a manager outlined eight weeks ago, Mozilla is taking a cautious approach to rolling out the changed Firefox. Mozilla has talked about a multi-process Firefox since 2009. As a general rule, the Chrome approach uses more device memory than the Safari model. Meanwhile, Chrome assigns a new rendering process to each new tab. Safari relies on a single process for the rendering engine, then spawns a new process for each tab's content. Other browsers, including Apple's Safari and Google's Chrome, already support multiple processes, albeit differently. The practice lets the browser take advantage of multi-processor systems for heightened performance, and segregates the browser's user interface (UI) and content to keep Firefox from fully crashing when a website or web app fails. "Electrolysis" - "e10s" in shorthand - has been Mozilla's long-term project to separate Firefox's operation into more than one CPU process.
0 kommentar(er)
