Bug 1300355 - Part 1: Increase frequency of GC/CC during reftests. r=dbaron
authorMatt Woodrow <mwoodrow@mozilla.com>
Wed, 28 Sep 2016 13:29:46 +1300
changeset 346038 a519934c735bc33a2e537aa585c3ab5c26da21c3
parent 346037 ee6ba4fcb76f65197aac3a7c329cd5942686e8a1
child 346039 3bd400108a21da50ce97ee2b1af553dadfb732f3
push id31452
push usercbook@mozilla.com
push dateMon, 06 Mar 2017 09:54:03 +0000
treeherdermozilla-central@966464a68a2c [default view] [failures only]
perfherder[talos] [build metrics] [platform microbench] (compared to previous push)
reviewersdbaron
bugs1300355
milestone54.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 1300355 - Part 1: Increase frequency of GC/CC during reftests. r=dbaron
layout/tools/reftest/reftest-content.js
--- a/layout/tools/reftest/reftest-content.js
+++ b/layout/tools/reftest/reftest-content.js
@@ -138,17 +138,17 @@ function SetFailureTimeout(cb, timeout)
 }
 
 function StartTestURI(type, uri, timeout)
 {
     // The GC is only able to clean up compartments after the CC runs. Since
     // the JS ref tests disable the normal browser chrome and do not otherwise
     // create substatial DOM garbage, the CC tends not to run enough normally.
     ++gTestCount;
-    if (gTestCount % 3000 == 0) {
+    if (gTestCount % 1000 == 0) {
         CU.forceGC();
         CU.forceCC();
     }
 
     // Reset gExplicitPendingPaintCount in case there was a timeout or
     // the count is out of sync for some other reason
     if (gExplicitPendingPaintCount != 0) {
         LogWarning("Resetting gExplicitPendingPaintCount to zero (currently " +