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

Mulongo oyo etiyamaki na archive. Tuna motuna mosusu soki osengeli na lisalisi

Multiprocess still disabled on Firefox 50

  • 2 biyano
  • 1 eza na nkokoso oyo
  • 5 views
  • Eyano yasuka ya M_W99

M_W99
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!

Solution eye eponami

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.
Tanga eyano oyo ndenge esengeli 👍 2

All Replies (2)

supportneeded
supportneeded
more options

Solution eye oponami

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.
M_W99
M_W99 Nkolo motuna
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.