Bug 1410376 - Disable e10s for non-Firefox Gecko users. r=Felipe draft
authorBlake Kaplan <mrbkap@gmail.com>
Fri, 20 Oct 2017 10:52:26 -0700
changeset 684063 46595d72327eaabbac4f7cc89eff5dfe755fac99
parent 683863 d1e995c8640a191cd127e87273ec96cb2fabffa9
child 736793 917fa2785871830c38ca58abc7ac3e1de67895ca
push id85534
push userbmo:mrbkap@mozilla.com
push dateFri, 20 Oct 2017 17:54:02 +0000
reviewersFelipe
bugs1410376, 1406212
milestone58.0a1
Bug 1410376 - Disable e10s for non-Firefox Gecko users. r=Felipe This also broke Thunderbird. I'm not entirely sure what's happening on Android, but I guess it's reading the pref and doing more work? None of the other changes from bug 1406212 should affect Android in the slightest. MozReview-Commit-ID: 7z5ysTDGSh
modules/libpref/init/all.js
--- a/modules/libpref/init/all.js
+++ b/modules/libpref/init/all.js
@@ -3357,16 +3357,19 @@ pref("dom.ipc.scheduler.chaoticSchedulin
 pref("svg.disabled", false);
 
 // Override default dom.ipc.processCount for some remote content process types.
 pref("dom.ipc.processCount.webLargeAllocation", 10);
 
 // Enable the Large-Allocation header
 pref("dom.largeAllocationHeader.enabled", true);
 
+// Disable e10s for Gecko by default. This is overridden in firefox.js.
+pref("browser.tabs.remote.autostart", false);
+
 // Pref to control whether we use separate content processes for top-level load
 // of file:// URIs.
 pref("browser.tabs.remote.separateFileUriProcess", true);
 
 // Pref that enables top level web content pages that are opened from file://
 // URI pages to run in the file content process.
 // This has been added in case breaking any window references between these
 // sorts of pages, which we have to do when we run them in the normal web