Multiprocess still says disabled by addons after updating to Firefox 49
I heard about multiprocess support (Electrolysis) when Firefox 48 came out and was hoping to be able to use it, but it kept telling me that it was disabled by addons. Being as it was just rolling out, I decided to wait until the next big update before trying to enable it again.
When the Firefox 49 update came out today I made sure that all my addons were supported and then updated. However, even now it still says disabled by addons, even in Safe Mode.
Is there something else I have to switch on in about:config? Any help would be appreciated, thanks!
Ŋuɖoɖo si wotia
hi M_W99, making firefox multiprocess (codename e10s) is the biggest architectural change that firefox has undergone ever, so we are rolling out these changes gradually to ensure that we are not breaking the browsing experience of our users.
in regards to addons, e10s and firefox 49 to my knowledge we will enable e10s by default for addon users too, but only for users with a small sample of manually whitelisted addons (Greasemonkey, Download YouTube Videos as MP4, Video Download Helper, Lightbeam, Adblock Plus, uBlock Origin, Emoji Cheatsheet, Awesome Screenshot Plus, PersonasPlus, Add-on Compatibility Reporter) and webextensions.
in subsequent releases we plan to extend the coverage - if everything goes to plan in firefox 50 e10s will be enabled for users with any extensions marked as multiprocess compatible: https://docs.google.com/spreadsheets/d/1OFYrrvAFg8y1mZOEbuIR1axxtV8eul_be6ad9fe8JB0/edit#gid=1952061950
Xle ŋuɖoɖo sia le goya me 👍 2All Replies (4)
I'm able to toggle "extensions.e10sBlockedByAddons" to false and about:support says enabled by user. Is this considered "force enabling"?
Ɖɔɖɔɖo si wotia
hi M_W99, making firefox multiprocess (codename e10s) is the biggest architectural change that firefox has undergone ever, so we are rolling out these changes gradually to ensure that we are not breaking the browsing experience of our users.
in regards to addons, e10s and firefox 49 to my knowledge we will enable e10s by default for addon users too, but only for users with a small sample of manually whitelisted addons (Greasemonkey, Download YouTube Videos as MP4, Video Download Helper, Lightbeam, Adblock Plus, uBlock Origin, Emoji Cheatsheet, Awesome Screenshot Plus, PersonasPlus, Add-on Compatibility Reporter) and webextensions.
in subsequent releases we plan to extend the coverage - if everything goes to plan in firefox 50 e10s will be enabled for users with any extensions marked as multiprocess compatible: https://docs.google.com/spreadsheets/d/1OFYrrvAFg8y1mZOEbuIR1axxtV8eul_be6ad9fe8JB0/edit#gid=1952061950
If you want more background information about this have you already seen
- Electrolysis https://wiki.mozilla.org/E10s#Force_Enable
- What’s Next for Multi-process Firefox https://blog.mozilla.org/futurereleases/2016/08/02/whats-next-for-multi-process-firefox/
philipp said
hi M_W99, making firefox multiprocess (codename e10s) is the biggest architectural change that firefox has undergone ever, so we are rolling out these changes gradually to ensure that we are not breaking the browsing experience of our users. in regards to addons, e10s and firefox 49 to my knowledge we will enable e10s by default for addon users too, but only for users with a small sample of manually whitelisted addons (Greasemonkey, Download YouTube Videos as MP4, Video Download Helper, Lightbeam, Adblock Plus, uBlock Origin, Emoji Cheatsheet, Awesome Screenshot Plus, PersonasPlus, Add-on Compatibility Reporter) and webextensions. in subsequent releases we plan to extend the coverage - if everything goes to plan in firefox 50 e10s will be enabled for users with any extensions marked as multiprocess compatible: https://docs.google.com/spreadsheets/d/1OFYrrvAFg8y1mZOEbuIR1axxtV8eul_be6ad9fe8JB0/edit#gid=1952061950
That answers my question. Thank you very much!