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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgnKH_rAkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg7IXmkggM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg3KLw9AgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgnPXEmgoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgnKS3xwkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg7Iuw6QsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg7MfB8QoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg3KLBowoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgnJX_lwkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgnLjzkQsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg7IXm0goM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg7IXmkgoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg3Ie-vAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg7MXu_wsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgnLf7qwoM


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

chromium-rel-mac-retina
chromium-rel-mac11-pro
chromium-rel-mac12
chromium-rel-mac12-mini-8gb
chromium-rel-win10
chromium-rel-win7-dual
chromium-rel-win7-gpu-ati
chromium-rel-win7-gpu-intel
chromium-rel-win7-gpu-nvidia
chromium-rel-win7-x64-dual
chromium-rel-win8-dual
linux-release
win-high-dpi

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

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

Suspected Commit
  Author : ksakamoto
  Commit : dd3783e3fbc682b2140333c56f446c1570cbe4b8
  Date   : Thu Mar 30 08:57:46 2017
  Subject: Detached FrameLoader should not log snapshot trace events

Bisect Details
  Configuration: win_x64_perf_bisect
  Benchmark    : system_health.common_desktop
  Metric       : timeToFirstContentfulPaint_avg/browse_news/browse_news_nytimes
  Change       : 159.67% | 393.08255452 -> 1020.70712963

Revision             Result                  N
chromium@460663      393.083 +- 42.6463      6      good
chromium@460697      398.036 +- 40.5994      6      good
chromium@460702      426.26 +- 128.596       6      good
chromium@460703      1020.92 +- 197.482      6      bad       <--
chromium@460704      950.477 +- 72.4211      6      bad
chromium@460706      1056.79 +- 510.88       6      bad
chromium@460714      1115.42 +- 471.623      6      bad
chromium@460730      1020.71 +- 194.709      6      bad

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

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8983144367476943888

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5843655320928256


| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Speed>Bisection.  Thank you!