Bug 1505573 - [Mac] Enable sandbox early startup by default on all releases (ride the trains) r=Alex_Gaynor
authorHaik Aftandilian <haftandilian@mozilla.com>
Fri, 30 Nov 2018 13:55:13 +0000
changeset 505428 ab21bad9895d263a0cd717fd38960459413efc26
parent 505427 44cedf1935796806b9120fbdeeb3999e18788c5d
child 505429 8dfebfa481b127c422a703354d3b96d0d5d56ee2
push id10290
push userffxbld-merge
push dateMon, 03 Dec 2018 16:23:23 +0000
treeherdermozilla-beta@700bed2445e6 [default view] [failures only]
perfherder[talos] [build metrics] [platform microbench] (compared to previous push)
reviewersAlex_Gaynor
bugs1505573
milestone65.0a1
first release with
nightly linux32
nightly linux64
nightly mac
nightly win32
nightly win64
last release without
nightly linux32
nightly linux64
nightly mac
nightly win32
nightly win64
Bug 1505573 - [Mac] Enable sandbox early startup by default on all releases (ride the trains) r=Alex_Gaynor Let sandbox early startup ride the trains by setting security.sandbox.content.mac.earlyinit=true on all releases, not just Nightly. Differential Revision: https://phabricator.services.mozilla.com/D13470
browser/app/profile/firefox.js
--- a/browser/app/profile/firefox.js
+++ b/browser/app/profile/firefox.js
@@ -1023,17 +1023,17 @@ pref("security.sandbox.gpu.level", 0);
 
 // Controls whether we disable win32k for the GMP processes.
 // true means that win32k system calls are not permitted.
 // Note: win32k is currently _not_ disabled due to intermittent test failures,
 // where the GMP process fails very early. See bug 1449348.
 pref("security.sandbox.gmp.win32k-disable", false);
 #endif
 
-#if defined(NIGHTLY_BUILD) && defined(XP_MACOSX) && defined(MOZ_SANDBOX)
+#if defined(XP_MACOSX) && defined(MOZ_SANDBOX)
 // Start the Mac sandbox early during child process startup instead
 // of when messaged by the parent after the message loop is running.
 pref("security.sandbox.content.mac.earlyinit", true);
 #endif
 
 #if defined(XP_MACOSX) && defined(MOZ_SANDBOX) && defined(MOZ_CONTENT_SANDBOX)
 // This pref is discussed in bug 1083344, the naming is inspired from its
 // Windows counterpart, but on Mac it's an integer which means: