Pesquisar no apoio

Evite burlas no apoio. Nunca iremos solicitar que telefone ou envie uma mensagem de texto para um número de telefone ou que partilhe informações pessoais. Por favor, reporte atividades suspeitas utilizando a opção "Reportar abuso".

Saber mais

Multiprocess still disabled on Firefox 50

  • 2 respostas
  • 1 tem este problema
  • 4 visualizações
  • Última resposta por M_W99

more options

When Firefox 49 came out I made a similar question (https://support.mozilla.org/en-US/questions/1139788) and was told that if everything went as planned, Multiprocess would be enabled for all users with compatible addons on Firefox 50 when it came out.

Well, I updated to FF 50 and it still said "disabled by addons". I enabled it manually in about:config, but it turned back off the next day.

So, my question is: Does FF 50 fully support Multiprocess, or is it still something that only a few users have full access to? I don't understand why it says "disabled by addons" when all my addons are marked as compatible...

I've been looking forward to Multiprocess, Electrolysis, e10s, whatever you want to call it for awhile now, but it would appear that it still hasn't been totally released into the wild yet. Or is there something on my end that I need to change?

Thanks!

When Firefox 49 came out I made a similar question (https://support.mozilla.org/en-US/questions/1139788) and was told that if everything went as planned, Multiprocess would be enabled for all users with compatible addons on Firefox 50 when it came out. Well, I updated to FF 50 and it still said "disabled by addons". I enabled it manually in about:config, but it turned back off the next day. So, my question is: Does FF 50 fully support Multiprocess, or is it still something that only a few users have full access to? I don't understand why it says "disabled by addons" when all my addons are marked as compatible... I've been looking forward to Multiprocess, Electrolysis, e10s, whatever you want to call it for awhile now, but it would appear that it still hasn't been totally released into the wild yet. Or is there something on my end that I need to change? Thanks!

Solução escolhida

Going into about:config worked for me. Enabled stayed.

This was the fix I was given that worked:

   In the address bar, type about:config and press the Enter key.
   The about:config "This might void your warranty!" warning page may appear.
   Click I accept the risk! to continue to the about:config page.
   Search for e10s and set extensions.e10sBlocksenabling to false.
   Restart Firefox.
Ler esta resposta no contexto 👍 2

Todas as respostas (2)

more options

Solução escolhida

Going into about:config worked for me. Enabled stayed.

This was the fix I was given that worked:

   In the address bar, type about:config and press the Enter key.
   The about:config "This might void your warranty!" warning page may appear.
   Click I accept the risk! to continue to the about:config page.
   Search for e10s and set extensions.e10sBlocksenabling to false.
   Restart Firefox.
more options

supportneeded said

Going into about:config worked for me. Enabled stayed. This was the fix I was given that worked: In the address bar, type about:config and press the Enter key. The about:config "This might void your warranty!" warning page may appear. Click I accept the risk! to continue to the about:config page. Search for e10s and set extensions.e10sBlocksenabling to false. Restart Firefox.

Thanks, that worked.