Is e10s Electrolysis now on by default with FF57?

[ttggzz]

Hello, I'm a many window/huge tab count user, 10 year old core 2 duo laptop 64bit OS with 8GB ram. Some time ago Firefox was becoming so slow/freezing and crashing I started looking at recent computers on the used market [but really wanted to keep my current set up for another 5 years or so].

Anyway, somehow I discovered this "force-enable e10s" thing and was astonished, absolutely blown away by the speed/load increase. I'm talking it easily seemed like 10x faster and my windows/tabs were handled with ease.

http://techdows.com/2016/01/force-enabl ... refox.html

I still have this activated in about:config. Is that redundant now, am I messing something up by having that setting? I have been getting some freezing/crashing but I think it may be something else. For one thing I haven't found a decent "unload tab" add on since 57.

I thought Electrolysis was supposed to be "rolled out" in 2016 sometime. I don't really understand this stuff, I just use what I find that seems like it will do what I want.

http://techdows.com/2015/05/multiproces ... -date.html

thanks

[allande]

Most legacy extensions have glitches with e10s, so when it first rolled out, it was only for users who didn't have any extensions. There is no harm in forcing it on in Firefox 57+, but now that legacy extensions are gone it will be turned on for most users by default. If you are still having any sluggishness try disabling accessibility hooks:
https://support.mozilla.org/en-US/kb/ac ... y-services

[ttggzz]

Thanks allande

Most legacy extensions have glitches with e10s, so when it first rolled out, it was only for users who didn't have any extensions.

Yeah I remember reading about that before I first tried it and was mystified that it was working [spectacularly] with all my extensions still active. Not sure but strongly suspicious part of the problem for me now is I haven't found a decent tab unloader. Tried "tab suspender" and it was a colossal disaster.

If you are still having any sluggishness try disabling accessibility hooks:
https://support.mozilla.org/en-US/kb/ac ... y-services

I will look into that, thanks

[therube]

Disable (reset) your force, & restart FF.
See if e10s are still enabled.
If not, then FF (in its wisdom) might have some reason to think that it should not be enabled on your end.
And if they do that, & you don't agree, re-enable the force.

[ttggzz]

Disable (reset) your force, & restart FF.
See if e10s are still enabled.

Thanks therube, it had crossed my mind, will have to try it out.

[shirishag75]

there doesn't seem to be a browser.tabs.remote.force-enable by default in 57.0 .

On the other hand I see/saw this https://support.mozilla.org/en-US/questions/1185320 but doesn't make much sense to me but guess we are in transition mode so glitches are to be expected for probably couple of releases.

[ttggzz]

there doesn't seem to be a browser.tabs.remote.force-enable by default in 57.0 .

Ahh, good to know, thanks shirishag75.

Edit: just re-reading that, in addition I will mention that I believe that is another angle to my question. The link showed how to create that boolean preference, and the article was pre-Quantum. Sooo, if that preference must be created in 57 as well, then there is the question: is it not there because it is enabled permanently, unchangeable [or something like that]?

http://techdows.com/2016/01/force-enabl ... refox.html

On the other hand I see/saw this https://support.mozilla.org/en-US/questions/1185320 but doesn't make much sense to me but guess we are in transition mode so glitches are to be expected for probably couple of releases.

whoa... I will be examining that info, nice find. I am going to revert my settings if only to see if Quantum fixed my earlier freezing/speed issues. But it won't be a true test because I don't as of yet have a working tab unloader. Thankfully that will be changing as the wonderful "All Tabs Helper" will be [re]-adding unload tabs feature but not until firefox 58.