about:config ("browser.tabs.remote", "browser.tabs.remote.[autostart, etc.]") - this should be disabled (AFAIK) Topic is solved

[GMforker]

After switching from false to true (mistakenly) - the browser becomes unusable.

[New Tobin Paradigm]

Then don't enable them. There is a good reason why they are false by default but other reasons they exist.

Not really our job to keep you from shooting yourself in the foot while randomly flipping prefs on and off in about:config.. It is pretty well understood by all that if you don't actually know what you are doing in there you can and likely will screw yourself over eventually while messing about in it.

There is a reason why every now and again we remind people of this when we even direct users to change something directly in about:config.

[GMforker]

Then don't enable it.

IMHO: This answer is OK, but it is not the solution.

[Latitude]

After reading Tycho sub-forum, I stumbled in this thread:

viewtopic.php?f=56&t=12946

It is about "browser.tabs.remote" setting which crashed PM.

What is it? Is it about Electrolysis in PM?
According to Google Search, it is Electrolysis setting.

https://www.google.com/search?q=browser.tabs.remote

[New Tobin Paradigm]

This is correct. Please do not ever mess with the default settings for this. Obviously, it can put the platform into an unstable state because the application front end code is BARELY e10s aware and due to it's ported nature it has no semblance of a much later e10s basis.

Just do yourself a favor and ignore it.. We do not and will not ever support e10s and if we get the chance we will kill it on a code level.

EDIT: Merged back into original topic.. No need for the same thing to be discussed in different threads.

[Moonchild]

Then don't enable it.

IMHO: This answer is OK, but it is not the solution.

The solution is to heed the warning when opening about:config.
We will not be held responsible if you get eaten, roasted, or otherwise molested by dragons.