Mozilla Announces Project Fission, a Project To Add True Multi-Process Support To Firefox (zdnet.com)

An anonymous reader quotes a report from ZDNet: After a year of secret preparations, Mozilla has publicly announced plans today to implement a "site isolation" feature, which works by splitting Firefox code in isolated OS processes, on a per-domain (site) basis. The concept behind this feature isn't new, as it's already present in Chrome, since May 2018. Currently, Firefox comes with one process for the browser's user interface, and a few (two to ten) processes for the Firefox code that renders the websites. With Project Fission (as this was named), Firefox split processes will change, and a separate one will be created for each website a user is accessing. This separation will be so fine-grained that just like in Chrome, if there's an iframe on the page, that iframe will receive its own process as well, helping protect users from threat actors that hide malicious code inside iframes (HTML elements that load other websites inside the current website). This is the same approach Chrome has taken with its "Site Isolation."

Comments

Chrome memory usage

[Anonymous Coward]

Firefox: Hold my beer.

I'm starting to hare firefox

[AndyKron]

Yippy. Another fucking update

Re:I'm starting to hare firefox

[Anonymous Coward]

Wait until Intel puts it on-die as part of their new IME. "The fastest most hyperthreaded browser-on-a-chip is now always on even when your machine is off! Swear to god, it's a feature! Sure someone asked for it!"

Re:Typical C(++) coders.

[AHuxley]

Time for an Ada browser on an Ada OS.