Firefox Fights Back - Firefox 57

tomseys · 08 Oct 2017

bo elam said:

No, the setting is not greyed out because of legacy extensions. To be able to change Content process limit you have to enable Multiprocess. You probably disabled Multiprocess in the past. If you enable Multiprocess, the setting becomes available. Is easy to test.

Bo

So then how do you enable multiprocess?

I can test it now that I am back on FF 56 - which seems to be faster than FF 57 btw.

When I was briefly on FF 57, I had the ability to change the multiprocess setting. And I also had no legacy extension on this.

Josey Wales · 08 Oct 2017

tomseys said:

So then how do you enable multiprocess? And how do you disable it for that matter? Please be explicit.

I can test it now that I am back on FF 56 - which seems to be faster than FF 57 btw. I don't know where they are getting twice the speed from. It certainly not in the startup or loading a page.

When I was briefly on FF 57, I had the ability to change the multiprocess setting. And I also had no legacy extension on this.

Fx 57 Beta 7 should be out tomorrow. In 56 you have to use about:config and change some things I think. I never used it.

tomseys · 08 Oct 2017

I think the setting is browser.tabs.remote.autostart

but it was already set to true... it's already on.. but FF is not allowing it.. prob because of incompatible add-ons

tomseys · 08 Oct 2017

bo elam said:

No, the setting is not greyed out because of legacy extensions. To be able to change Content process limit you have to enable Multiprocess. You probably disabled Multiprocess in the past. If you enable Multiprocess, the setting becomes available. Is easy to test.

Bo

Okay i did a test... I disabled my legacy add-ons, restarted FF 56 and now have control of electrolysis and its multiprocess setting. I can set it if I like. I renabled the legacy add-ons, restarted FF, and no longer can change the multiprocess setting. It is greyed out to 1.

Please note again that in both cases browser.tabs.remote.autostart is set to true (it is on)

Gotta be the legacy add-ons no?

bo elam · 08 Oct 2017

tomseys said:

So then how do you enable multiprocess?

I can test it now that I am back on FF 56 - which seems to be faster than FF 57 btw.

When I was briefly on FF 57, I had the ability to change the multiprocess setting. And I also had no legacy extension on this.

First, make sure you have Multiprocess disabled. Look in Firefox Help>Throbleshooting information. See what is says next to Multiprocess Windows. If its disabled, it ll say Disabled.

If it is, open about:config and search for "browser.tabs.remote.autostart". Changing browser.tabs.remote.autostart from false to true reenables Multiprocess. This is so unless you disabled Multiprocess via accessibility tools. Then it would have to be reenabled in another way.

Bo

RealJustMe · 08 Oct 2017

I love Firefox, I use Firefox a lot. I also have Chrome, but that's just there to have it.

BUT...

Today was the first time I ever had to downgrade firefox, because after it updated to version 56 I believe, it became super slow. I mean, I couldn't do jack with it.

I downgraded to 55.0.3, and now it's good again.

I'm not leaving Firefox, no way, but this was pretty bad. An update should make it better, not break it.

tomseys · 08 Oct 2017

bo elam said:

First, make sure you have Multiprocess disabled. Look in Firefox Help>Throbleshooting information. See what is says next to Multiprocess Windows. If its disabled, it ll say Disabled.

If Multiprocess show disabled, open about:config and search for "browser.tabs.remote.autostart". Changing browser.tabs.remote.autostart from false to true reenables Multiprocess. This is so unless you disabled Multiprocess via accessibility tools. Then you would have to reenable it another way.

Bo

Okay in about:config, that setting is set to true - it's always been true.

In about:support, it states: Multiprocess Windows: 0/1 (Disabled by add-ons)

So I guess it is disabled because of the legacy add-ons.

bruinator · 08 Oct 2017

bruinator said:

it can be done that way. Yes. I have done it in the past. Ignore previous post.

What i want to know, is there a way to replace opened tabs with new ones instead of adding to them? An extension use to be able to do it called openintabs-erase. Does anyone know if it is possible to accomplish this?

thx

Does anyone know if this is possible?

thx

bo elam · 08 Oct 2017

tomseys said:

Okay in about:config, that setting is set to true.

In about:support, it states: "0/1 (Disabled by add-ons)"

So I guess it is disabled because of the legacy add-ons.

No, your extensions being legacy has nothing to do. In your case if you want to change Content process limit, you ll have to figure out the addon thats disabling Multiprocess. Its very likely it is 1 addon and 1 addon alone thats causing it. I use 3 extensions, they all legacy, and I can play with Content process limit as long as I enable Multiprocess. Take a look.

Edit: Add picture and fix my reply after you edited the post I was replying to.

Bo

PaulGo · 08 Oct 2017

RealJustMe said:

I love Firefox, I use Firefox a lot. I also have Chrome, but that's just there to have it.

BUT...

Today was the first time I ever had to downgrade firefox, because after it updated to version 56 I believe, it became super slow. I mean, I couldn't do jack with it.

I downgraded to 55.0.3, and now it's good again.

I'm not leaving Firefox, no way, but this was pretty bad. An update should make it better, not break it.

I had the same problem. It turned out something in my configuration got messed up. Try either doing a refresh of or using a new configuration (by deleting your old configuration - save your bookmarks and passwords before you do this). With a new configuration Firefox 56 starts up and runs very quickly.