Firefox 63: Linux out-of-process extensions - gHacks Tech News

Firefox 63: Linux out-of-process extensions

Mozilla plans to enable out-of-process extensions for Firefox running on GNU/Linux systems in Firefox 63. The organization plans to release Firefox 63 on October 23, 2018 for all supported desktop and mobile operating systems.

Mozilla added multi-process capabilities to Firefox 49 and improved the functionality in future releases. Multi-process separates different parts of the web browser, for instance browser tabs and the core browser, to improve security and stability.

Work on Firefox's security sandbox continues, and so does work on moving additional elements to their own process. Mozilla added supported for out-of-process extensions in Firefox 56 on Windows, and added the functionality in Firefox 61 to installations of the web browser running on Mac OS X.

GNU/Linux, the last desktop operating system that Firefox supports, will get the out-of-process functionality for WebExtensions in Firefox 63 so that all desktop versions of the browser run extensions in their own process that is separate from browser tabs and the core browser.

The bug over on Bugzilla highlights the current status. It lists Firefox 63 as the target for the integration, and lists bugs that it depends on which Mozilla engineers need to get done before the feature can be rolled out to Firefox's Linux population.

Work on running WebExtensions out of process began three years ago.

The actual extension code will run in a content process. We'll do this using remote <browser> elements (and maybe remote moz-browser elements on b2g). The main process will load a process script into the extension process and the two processes will communicate using the process message manager.

Moving WebExtensions -- the only type of browser extensions all supported versions of Firefox support by the time Firefox 63 is released -- to a process improves security and stability of Firefox. The addition of another running process will increase memory usage somewhat; it depends entirely on the extensions installed in the browser.

firefox out-of-process linux

Linux users of Firefox who are adventurous can do the following to enable support for out of process extensions right away (note that this may work only in Nightly versions properly right now and not in stable versions).

  1. Load about:config?filter=extensions.webextensions.remote
  2. Double-click on the preference.

A value of true means that the functionality is enabled, a value of false that it is disabled. The about:config entry provides users with options to turn off the functionality if it causes issues or high RAM usage.

 

Summary
Firefox 63: Linux out-of-process extensions
Article Name
Firefox 63: Linux out-of-process extensions
Description
Mozilla plans to enable out-of-process extensions for the Firefox web browser running on GNU/Linux systems in Firefox 63.
Author
Publisher
Ghacks Technology News
Logo
Advertisement

We need your help

Advertising revenue is falling fast across the Internet, and independently-run sites like Ghacks are hit hardest by it. The advertising model in its current form is coming to an end, and we have to find other ways to continue operating this site.

We are committed to keeping our content free and independent, which means no paywalls, no sponsored posts, no annoying ad formats or subscription fees.

If you like our content, and would like to help, please consider making a contribution:


Previous Post: «
Next Post: »

Comments

  1. WebRender Enthusiast said on August 2, 2018 at 1:41 pm
    Reply

    So far with uBlock Origin+HTTPS Everywhere+Decentraleyes+NoScript = 180MiB (also don’t forget to enable WebRender), seems reasonable to me.

    1. michal_3city said on August 3, 2018 at 9:10 am
      Reply

      U mean like in of the process, right? Could anyone else confirm their memory usage, because I can’t replicate those even with just two first addons.

      Is it really a problem anyway? At least at new machines. On “legacy” ones you can tweak number of threads, disable some stuff, and firefox works good – at least not worse than so called lightweight browsers: midori, otter, palemoon (however this one seems to work nice on my older machines), qupzilla aka Falcon (well, that name is going to attract millions of users;)

      1. Anonymous said on August 3, 2018 at 1:35 pm
        Reply

        Minute after start with only this page: main firefox process 150MB, webextension process 150MB, 2 content processes 40MB + 20MB

        64bit linux, 17 extensions

Leave a Reply

Check the box to consent to your data being stored in line with the guidelines set out in our privacy policy

Please note that your comment may not appear immediately after you post it.