X
Tap here to go to the mobile version of the site.

Fóram Tacaíochta

Cuireadh an snáithe seo sa chartlann. Cuir ceist nua má tá cabhair uait.

Electrolysis disabled by addons after I've disabled all my addons?

Postáilte

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

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

Tuilleadh mionsonraí faoin chóras

Breiseáin Shuiteáilte

  • Adobe PDF Plug-In For Firefox and Netscape 15.17.20050
  • Intel web components for Intel® Identity Protection Technology
  • Intel web components updater - Installs and updates the Intel web components
  • LastPass Plugin
  • Shockwave Flash 22.0 r0
  • 5.1.41212.0
  • Unity Player 5.2.0f3

Feidhmchlár

  • Firefox 48.0.1
  • User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:48.0) Gecko/20100101 Firefox/48.0
  • URL Tacaíochta: https://support.mozilla.org/1/firefox/48.0.1/WINNT/en-US/

Eisínteachtaí

  • Firefox Hello 1.4.4 (loop@mozilla.org)
  • LastPass 4.1.26a (support@lastpass.com)
  • Multi-process staged rollout 1.1 (e10srollout@mozilla.org)
  • Pocket 1.0.4 (firefox@getpocket.com)
  • HTTPS-Everywhere 5.2.1 (https-everywhere@eff.org) (Neamhghníomhach)
  • Owl - For comfortable reading 1.3.2 (@owl-comfortable-reading-addon) (Neamhghníomhach)
  • Pushbullet 316 (jid1-BYcQOfYfmBMd9A@jetpack) (Neamhghníomhach)
  • uBlock Origin 1.8.4 (uBlock0@raymondhill.net) (Neamhghníomhach)
  • WOT 20151208 ({a0d7ccb3-214d-498b-b4aa-0e8fda9a7bf7}) (Neamhghníomhach)
  • YouTube High Definition 48.1 ({7b1bf0b6-a1b9-42b0-b75d-252036438bdc}) (Neamhghníomhach)

JavaScript

  • incrementalGCEnabled: True

Grafaic

  • adapterDescription: Intel(R) HD Graphics 4000
  • adapterDescription2: NVIDIA GeForce GT 650M
  • adapterDeviceID: 0x0166
  • adapterDeviceID2: 0x0fd1
  • adapterDrivers: igdumdim64 igd10iumd64 igd10iumd64 igdumdim32 igd10iumd32 igd10iumd32
  • adapterDrivers2: nvd3dumx,nvwgf2umx,nvwgf2umx nvd3dum,nvwgf2um,nvwgf2um
  • adapterRAM: Unknown
  • adapterRAM2: 2048
  • adapterSubsysID: 181d103c
  • adapterSubsysID2: 181d103c
  • adapterVendorID: 0x8086
  • adapterVendorID2: 0x10de
  • clearTypeParameters: Gamma: 2200 Pixel Structure: R ClearType Level: 100 Enhanced Contrast: 100
  • direct2DEnabled: True
  • directWriteEnabled: True
  • directWriteVersion: 6.2.9200.17568
  • driverDate: 5-16-2014
  • driverDate2: 8-11-2016
  • driverVersion: 10.18.10.3621
  • driverVersion2: 21.21.13.7254
  • info: {u'AzureCanvasAccelerated': 0, u'AzureCanvasBackend': u'direct2d 1.1', u'AzureFallbackCanvasBackend': u'cairo', u'AzureContentBackend': u'direct2d 1.1'}
  • isGPU2Active: False
  • numAcceleratedWindows: 1
  • numTotalWindows: 1
  • supportsHardwareH264: Yes; Using D3D9 API
  • webglRenderer: Google Inc. -- ANGLE (Intel(R) HD Graphics 4000 Direct3D11 vs_5_0 ps_5_0)
  • windowLayerManagerRemote: True
  • windowLayerManagerType: Direct3D 11

Sainroghanna Athraithe

Éagsúil

  • User JS: No
  • Inrochtaineacht: Níl
FredMcD
  • Top 10 Contributor
4227 réiteach 59011 freagra
Start '''[https://support.mozilla.org/en-US/kb/troubleshoot-firefox-issues-using-safe-mode Firefox in Safe Mode]''' {web Link} by holding down the '''<Shift><br> ''(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'''

Úinéir na ceiste

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.

''FredMcD [[#answer-908991|said]]'' <blockquote> Start '''[https://support.mozilla.org/en-US/kb/troubleshoot-firefox-issues-using-safe-mode Firefox in Safe Mode]''' {web Link} by holding down the '''<Shift><br> ''(Mac=Options)'' ''' key, and then starting Firefox. A small dialog should appear. Click '''Start In Safe Mode''' (not Refresh). Is the problem still there? </blockquote> Yes, it still says disabled by addons even in Safe Mode.

Athraithe ag M_W99 ar

the-edmeister
  • Top 25 Contributor
  • Moderator
5395 réiteach 40084 freagra

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

'''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 [https://addons.mozilla.org/en-US/firefox/addon/menu-filter/ Menu Filter extension]. When I removed Menu Filter the '''extensions.e10sBlockedByAddons''' pref automatically toggled back to '''false'''

Úinéir na ceiste

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?

''the-edmeister [[#answer-909087|said]]'' <blockquote> '''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 [https://addons.mozilla.org/en-US/firefox/addon/menu-filter/ Menu Filter extension]. When I removed Menu Filter the '''extensions.e10sBlockedByAddons''' pref automatically toggled back to '''false''' </blockquote> Ok, so I actually have to remove them, not just disable, correct?

Úinéir na ceiste

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!

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!