All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=742342

(For debugging:) Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?sid=bc71c30ae1c45ac8c0a4e5ca62c4548bc865dd7dff989e46a2d91117d625f1dc


Bot(s) for this bug's original alert(s):

chromium-rel-mac11-air
win-high-dpi

Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8974178152456196976

=== BISECT JOB RESULTS ===
Perf regression found with culprit

Suspected Commit
  Author : Marc Treib
  Commit : da2086682fef5cc44b539dc4bdc63af380e2988b
  Date   : Tue Jul 11 09:16:07 2017
  Subject: Fieldtrial testing config for CaptureThumbnailOnLoadFinished

Bisect Details
  Configuration: mac_air_perf_bisect
  Benchmark    : jetstream
  Metric       : Score/Score
  Change       : 3.82% | 125.166666667 -> 120.388888889

Revision             Result                  N
chromium@485534      125.167 +- 2.14735      6      good
chromium@485552      124.611 +- 2.88354      6      good
chromium@485561      124.778 +- 1.12217      6      good
chromium@485566      124.778 +- 1.5396       6      good
chromium@485567      124.167 +- 2.97209      6      good
chromium@485568      120.0 +- 1.49071        6      bad       <--
chromium@485570      121.0 +- 3.12694        6      bad
chromium@485605      120.389 +- 2.9596       6      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests jetstream

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8974178152456196976


For feedback, file a bug with component Speed>Bisection