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

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

Suspected Commit
  Author : Marc Treib
  Commit : 6fb10fe065b1cfe4c4aa691c31c03e7387a72d40
  Date   : Mon Jun 26 18:39:55 2017
  Subject: Fieldtrial testing config for CaptureThumbnailOnLoadFinished

Bisect Details
  Configuration: mac_10_12_perf_bisect
  Benchmark    : system_health.memory_desktop
  Metric       : memory:chrome:all_processes:reported_by_chrome:malloc:effective_size_avg/browse_news/browse_news_reddit
  Change       : 6.86% | 48700547.5556 -> 52041290.6667

Revision             Result                   N
chromium@482287      48700548 +- 1902833      9       good
chromium@482328      49123951 +- 4172417      14      good
chromium@482334      48578714 +- 1426610      6       good
chromium@482335      48980406 +- 1294763      6       good
chromium@482336      50226321 +- 651641       6       bad       <--
chromium@482337      50658185 +- 3338502      6       bad
chromium@482339      49700621 +- 2119840      14      bad
chromium@482349      49755786 +- 2173036      14      bad
chromium@482369      50018264 +- 1355807      9       bad
chromium@482451      52041291 +- 6058859      6       bad

Please refer to the following doc on diagnosing memory regressions:
  https://chromium.googlesource.com/chromium/src/+/master/docs/memory-infra/memory_benchmarks.md

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=browse.news.reddit system_health.memory_desktop

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

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


For feedback, file a bug with component Speed>Bisection