3 ms·

Electrolysis has been enabled by default since Firefox 48. Source: https://wiki.mozilla.org/Electrolysis#Schedule https://wiki.mozilla.org/Electrolysis#Schedule

by rvern 9y ago

Electrolysis has been enabled by default since Firefox 48. Source: https://wiki.mozilla.org/Electrolysis#Schedule https://wiki.mozilla.org/Electrolysis#Schedule.

dstaley 9y ago
> As of Firefox 54+ (early 2017), our Multi-Content process model is currently being tested on Nightly (4 processes). Four content processes will be enabled on 54 Aurora and if stable enough, we will begin to roll it out in Firefox 54 Beta experiments. This seems to be the case because I downloaded Firefox 53 for the first time on my new MacBook Pro and e10s wasn't enabled. I had to go to about:config and enable it manually.
- xenithorb 9y ago
  You may have an extension blocking it. Get the addon compatability plugin.
- bzbarsky 9y ago
  Firefox 52 shipped with e10s enabled by default for all users except those who are on Windows XP, have a windows machine with a touchscreen, or have extensions that are not compatible with e10s. It uses one browser UI process and one web content process. Firefox 54 has e10s-multi, with multiple web content processes. If you go to about:support in your Firefox 53, the "Multiprocess Windows" item in the first section ("Application Basics") should tell you why e10s is disabled for you, if it's disabled.
  - dstaley 9y ago
    The only thing it says for me is "0/1 (Disabled)". [0] Edit: Ah, so this is weird. It looks like e10s isn't enabled when you first run Firefox. You need to quit, and then relaunch. On the second launch e10s is then enabled. This explains why I thought it was disabled by default (since it was my first time running Firefox on this machine). [0] https://gist.github.com/dstaley/b17ce52947cf520ca793d545daee5302 https://gist.github.com/dstaley/b17ce52947cf520ca793d545daee...
    - bzbarsky 9y ago
      "Disabled" means there was an explicit pref set to disable it. I can't tell from over here what preferences you changed and in what order and when. You said "I had to go to about:config and enable it manually"... did you restart after that? e10s pref changes require a restart to take effect. What was the state of the preferences before you did that, if you remember? In any case, glad to hear it's working for you now.
- deleted 9y ago
  [deleted]

by rvern 9y ago

Electrolysis has been enabled by default since Firefox 48. Source: https://wiki.mozilla.org/Electrolysis#Schedule https://wiki.mozilla.org/Electrolysis#Schedule.

dstaley 9y ago

> As of Firefox 54+ (early 2017), our Multi-Content process model is currently being tested on Nightly (4 processes). Four content processes will be enabled on 54 Aurora and if stable enough, we will begin to roll it out in Firefox 54 Beta experiments. This seems to be the case because I downloaded Firefox 53 for the first time on my new MacBook Pro and e10s wasn't enabled. I had to go to about:config and enable it manually.

xenithorb 9y ago
You may have an extension blocking it. Get the addon compatability plugin.
bzbarsky 9y ago
Firefox 52 shipped with e10s enabled by default for all users except those who are on Windows XP, have a windows machine with a touchscreen, or have extensions that are not compatible with e10s. It uses one browser UI process and one web content process. Firefox 54 has e10s-multi, with multiple web content processes. If you go to about:support in your Firefox 53, the "Multiprocess Windows" item in the first section ("Application Basics") should tell you why e10s is disabled for you, if it's disabled.
- dstaley 9y ago
  The only thing it says for me is "0/1 (Disabled)". [0] Edit: Ah, so this is weird. It looks like e10s isn't enabled when you first run Firefox. You need to quit, and then relaunch. On the second launch e10s is then enabled. This explains why I thought it was disabled by default (since it was my first time running Firefox on this machine). [0] https://gist.github.com/dstaley/b17ce52947cf520ca793d545daee5302 https://gist.github.com/dstaley/b17ce52947cf520ca793d545daee...
  - bzbarsky 9y ago
    "Disabled" means there was an explicit pref set to disable it. I can't tell from over here what preferences you changed and in what order and when. You said "I had to go to about:config and enable it manually"... did you restart after that? e10s pref changes require a restart to take effect. What was the state of the preferences before you did that, if you remember? In any case, glad to hear it's working for you now.
deleted 9y ago
[deleted]