Avatar for Username

Etsi tuesta

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.

Lue lisää

Ketju on arkistoitu. Esitä kysymys, jos tarvitset apua.

extensions.e10sBlockedByAddons keeps resetting to 'true' - why ?

  • 1 vastaus
  • 1 henkilöllä on sama ongelma
  • 2 näyttöä
  • Viimeisin kirjoittaja cor-el

e10s-now
e10s-now
more options

i have only chosen addons that, according to mozilla's 'addon compatibility reporter' are all compatible with multiprocess. and i don't even have any non-compatible addons installed. i can confirm that e10s is definitely enabled when checking about:support. however, any time i click enable/disable on an addon, the about:config option extensions.e10sBlockedByAddons will reset to 'true' the next time firefox is started !! why ??? sometimes this seems to reset subtley in the background, and i don't notice straight away. and even when i do notice i have to restart the whole browser >.< what a pain

i have only chosen addons that, according to mozilla's 'addon compatibility reporter' are all compatible with multiprocess. and i don't even have any non-compatible addons installed. i can confirm that e10s is definitely enabled when checking about:support. however, any time i click enable/disable on an addon, the about:config option extensions.e10sBlockedByAddons will reset to 'true' the next time firefox is started !! why ??? sometimes this seems to reset subtley in the background, and i don't notice straight away. and even when i do notice i have to restart the whole browser >.< what a pain

Muokattu , muokkaaja e10s-now

Valittu ratkaisu

See also:

You can consider to set the pref to false via the user.js file in the profile folder. That way it is at least disabled on a Firefox start.

Lue tämä vastaus kontekstissaan 👍 0

Kaikki vastaukset (1)

cor-el
cor-el
  • Moderator
  • Top 10 Contributor
more options

Valittu ratkaisu

See also:

You can consider to set the pref to false via the user.js file in the profile folder. That way it is at least disabled on a Firefox start.