tools/benchmarks: Fix failures in image decoding measurements.

content/browser/gpu/compositor_util.cc

Index: content/browser/gpu/compositor_util.cc
diff --git a/content/browser/gpu/compositor_util.cc b/content/browser/gpu/compositor_util.cc
index 1298d758be69ca71da7af70e1afe58c859c8ec19..011454be101ffc3190e175784803f92300f87892 100644
--- a/content/browser/gpu/compositor_util.cc
+++ b/content/browser/gpu/compositor_util.cc
@@ -284,6 +284,10 @@ bool IsMainFrameBeforeActivationEnabled() {
 }
 
 bool IsCheckerImagingEnabled() {
+  if (base::CommandLine::ForCurrentProcess()->HasSwitch(
+          cc::switches::kDisableCheckerImaging))
+    return false;
+
   if (base::CommandLine::ForCurrentProcess()->HasSwitch(

[cblume, 2017/06/28 19:17:26]

Just to make sure I understand this correctly,

We have a command line switch to disable.
We also have one to enable.

So presumably we could do a slow rollout where we enable for a small number of
users. But the user could override that and disable if needed.

That is, if both disable and enable are specified, the disable wins.

[Khushal, 2017/06/28 20:29:55]

The command line switches are not exposed to the users, there is no entry in
chrome:flags for them. These are just for dev testing.

We are already doing a slow roll out for this on canary using a finch
experiment.

           cc::switches::kEnableCheckerImaging))
     return true;