Going forward, Multi-process can't be turned off anymore in Firefox

[harlan4096]

Mozilla plans to remove configuration options in upcoming versions of the Firefox web browser that allow users to disable the browser's multi-process architecture.

Mozilla introduced the multi-process architecture in the Firefox web browser in 2016. Firefox would use multiple processes to divide loaded sites between them and use different processes for the browser's own functionality.

While that increased memory usage, it also meant that Firefox would become more stable in the process and less prone to site crashes taking the entire browser with them. Mozilla's implementation was different to Google's. Chrome uses one process per site, Firefox puts multiples sites in a single process.

Firefox's Multi-process architecture received numerous improvements over the years. Mozilla added more processes to it and introduced a sandbox security feature later on that depended on it.

Mozilla plans to remove two Firefox preferences from any version of the web browser going forward. The change is planed for Firefox 68.

* browser.tabs.remote.force-enable -- Enforces the use of multi-process in Firefox if it is not enabled by default, e.g. because of accessibility.

* browser.tabs.remote.force-disable -- Disables multi-process in the Firefox web browser.

Continue Reading