Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

Avatar for Username

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Natao arisiva ity resaka mitohy ity. Mametraha fanontaniana azafady raha mila fanampiana.

Multiprocess won't enable with addons enabled, even though the addons are compatible.

  • 1 valiny
  • 2 manana an'ity olana ity
  • 1 view
  • Valiny farany nomen'i jebbush

jebbush
jebbush
more options

I can't get electrolysis/e10s/multiprocess to not be disabled by add-ons. Running on Debian.

So, I upgraded to FF50 (From the Debian unstable repos, 50.0.2 according to the repo and the about: page), and flipped the about:config key browser.tabs.remote.autostart to True.

Looking at the "Multiprocess Windows" field at the about:support page it tells me that it's enabled properly, with all my addons disabled.

But if I enable any addon (I've tried with every addon installed that the compatibility reporter tells me is compatible, you can see a list in the troubleshooting information) and restart the browser, the about:support page tells me that multiprocessing is "Disabled by add-on".

From reading at the mozilla wiki (https://wiki.mozilla.org/Electrolysis) and generally around the web, it seems that from version 50 and on, e10s should be working with add-ons as long as they are multiprocessing compatible, which the Add-On Compatibility Reporter (https://addons.mozilla.org/en-US/firefox/addon/add-on-compatibility-reporter) tells me all of my add-ons are. (Except the DOM inspector, which I only enable when I need anyway)

Is there something I have overlooked? Something more that I should try?

Troubleshooting information is with the Add-On Compatibility Reporter enabled, and all other add-ons disabled.

I can't get electrolysis/e10s/multiprocess to not be disabled by add-ons. Running on Debian. So, I upgraded to FF50 (From the Debian unstable repos, 50.0.2 according to the repo and the about: page), and flipped the about:config key browser.tabs.remote.autostart to True. Looking at the "Multiprocess Windows" field at the about:support page it tells me that it's enabled properly, with all my addons disabled. But if I enable any addon (I've tried with every addon installed that the compatibility reporter tells me is compatible, you can see a list in the troubleshooting information) and restart the browser, the about:support page tells me that multiprocessing is "Disabled by add-on". From reading at the mozilla wiki (https://wiki.mozilla.org/Electrolysis) and generally around the web, it seems that from version 50 and on, e10s should be working with add-ons as long as they are multiprocessing compatible, which the Add-On Compatibility Reporter (https://addons.mozilla.org/en-US/firefox/addon/add-on-compatibility-reporter) tells me all of my add-ons are. (Except the DOM inspector, which I only enable when I need anyway) Is there something I have overlooked? Something more that I should try? Troubleshooting information is with the Add-On Compatibility Reporter enabled, and all other add-ons disabled.

Novain'i jebbush t@

All Replies (1)

jebbush
jebbush Tompon'ny fanontaniana
more options

Also, I'm aware of the force enable option, I'd just like to try and see if there's a problem that causes this or if it's just a weird bug. If there's a problem that disables e10s, there's probably a reason for doing so, meaning a reason not to force enable.