Electrolysis disabled by addons after I've disabled all my addons?
I've been trying to find a solution to my slow Firefox UI and came across Electrolysis. I have the latest version of Firefox 48.0.1 and I've set browser.tabs.remote.autostart to true. After doing that it said it was disabled by addons in about:support, so I disabled all my addons and restarted Firefox. Even after disabling all my addons, it still says "disabled by addons".
I know that it's possible to force-enable it, but I'd rather find a real solution rather than just forcing it.
Any help would be appreciated. Thanks!
Here's my data from about:support http://hastebin.com/ayufefoyeb.avrasm
All Replies (5)
Start Firefox in Safe Mode {web Link} by holding down the <Shift>
(Mac=Options) key, and then starting Firefox.
A small dialog should appear. Click Start In Safe Mode (not Refresh).
Is the problem still there?
https://support.mozilla.org/en-US/kb/websites-look-wrong-or-appear-differently
https://support.mozilla.org/en-US/kb/firefox-slow-how-make-it-faster
https://support.mozilla.org/en-US/kb/firefox-uses-too-many-cpu-resources-how-fix
https://support.mozilla.org/en-US/kb/firefox-hangs-or-not-responding
https://support.mozilla.org/kb/Firefox+is+already+running+but+is+not+responding
FredMcD said
Start Firefox in Safe Mode {web Link} by holding down the <Shift>
(Mac=Options) key, and then starting Firefox. A small dialog should appear. Click Start In Safe Mode (not Refresh). Is the problem still there?
Yes, it still says disabled by addons even in Safe Mode.
Modified by M_W99
e10s is experimental at this time - "things" will change a bit with each new full release version.
Disabled or not the current implementation of e10s will disable will disable itself upon installation when it detects any extensions beyond the 3 "default" extensions; at least as I observed with a fresh installation and with a a new Profile. I installed one extension to "test" what would happen. e10s was disabled altogether. Then I disabled that one extension and toggled extensions.e10sBlockedByAddons to false, when I restarted Firefox it went back to true all by itself.
If you want e10s to be active you need remove the offending extensions. I ran into this situation with the Menu Filter extension. When I removed Menu Filter the extensions.e10sBlockedByAddons pref automatically toggled back to false
the-edmeister said
e10s is experimental at this time - "things" will change a bit with each new full release version. Disabled or not the current implementation of e10s will disable will disable itself upon installation when it detects any extensions beyond the 3 "default" extensions; at least as I observed with a fresh installation and with a a new Profile. I installed one extension to "test" what would happen. e10s was disabled altogether. Then I disabled that one extension and toggled extensions.e10sBlockedByAddons to false, when I restarted Firefox it went back to true all by itself. If you want e10s to be active you need remove the offending extensions. I ran into this situation with the Menu Filter extension. When I removed Menu Filter the extensions.e10sBlockedByAddons pref automatically toggled back to false
Ok, so I actually have to remove them, not just disable, correct?
I removed Pushbullet, WOT, HTTPS Everywhere, and Owl, all of which weren't listed on http://arewee10syet.com/
I currently have LastPass, uBlock Origin, and YouTube High Definition, all of which are listed as supporting es10 and about:support still says disabled by addons.
I'm able to toggle extensions.e10sBlockedByAddons to false and about:support says enabled by user. What's the difference between doing that and force enabling it?
Thanks!