Backed out changeset 049ef1d4eb26 (bug 900784) on suspicion of letting devtools' browser_dbg_blackboxing-05.js frequently fail. r=backout
authorSebastian Hengst <archaeopteryx@coole-files.de>
Wed, 23 Aug 2017 11:40:52 +0200
changeset 376237 b911a4c97fde5d8bdeebfd5d0266ee9f7b9e59b2
parent 376236 7c50f0c999c5bf8ee915261997597a5a9b8fb2ae
child 376238 3bb3fe1a6c7fdbf87967d3687b47fb0235bdb775
child 376320 7aeb84cb7416a0b88ec1a16276170eccf157d820
push id94066
push userarchaeopteryx@coole-files.de
push dateWed, 23 Aug 2017 10:51:56 +0000
treeherdermozilla-inbound@3bb3fe1a6c7f [default view] [failures only]
perfherder[talos] [build metrics] [platform microbench] (compared to previous push)
reviewersbackout
bugs900784
milestone57.0a1
backs out049ef1d4eb2690857f88b03ea7bfeeb130ea2834
first release with
nightly linux32
b911a4c97fde / 57.0a1 / 20170823100553 / files
nightly linux64
b911a4c97fde / 57.0a1 / 20170823100553 / files
nightly mac
b911a4c97fde / 57.0a1 / 20170823100553 / files
nightly win32
b911a4c97fde / 57.0a1 / 20170823100553 / files
nightly win64
b911a4c97fde / 57.0a1 / 20170823100553 / files
last release without
nightly linux32
nightly linux64
nightly mac
nightly win32
nightly win64
releases
nightly linux32
nightly linux64
nightly mac
nightly win32
nightly win64
Backed out changeset 049ef1d4eb26 (bug 900784) on suspicion of letting devtools' browser_dbg_blackboxing-05.js frequently fail. r=backout MozReview-Commit-ID: J4ZRfyu0AAf
modules/libpref/init/all.js
--- a/modules/libpref/init/all.js
+++ b/modules/libpref/init/all.js
@@ -213,17 +213,17 @@ pref("dom.keyboardevent.dispatch_during_
 // causes a separate compartment for each (addon, global) combination, which may
 // significantly increase the number of compartments in the system.
 pref("dom.compartment_per_addon", true);
 
 // Whether to enable the JavaScript start-up cache. This causes one of the first
 // execution to record the bytecode of the JavaScript function used, and save it
 // in the existing cache entry. On the following loads of the same script, the
 // bytecode would be loaded from the cache instead of being generated once more.
-pref("dom.script_loader.bytecode_cache.enabled", true);
+pref("dom.script_loader.bytecode_cache.enabled", false);
 
 // Ignore the heuristics of the bytecode cache, and always record on the first
 // visit. (used for testing purposes).
 
 // Choose one strategy to use to decide when the bytecode should be encoded and
 // saved. The following strategies are available right now:
 //   * -2 : (reader mode) The bytecode cache would be read, but it would never
 //          be saved.