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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgoKOPtQkM


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

android-nexus9

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

=== BISECT JOB RESULTS ===
Perf regression found but unable to narrow commit range

Bisect Details
  Configuration: android_nexus9_perf_bisect
  Benchmark    : blink_perf.parser
  Metric       : iframe-append-remove/iframe-append-remove

Suspected Commit Range
  19 commits in range
  https://chromium.googlesource.com/chromium/src/+log/0635307354bc4b946cb6bf7855a9c133862f02e8..0deb194b2774d9a68a7fcba1d4fe17477767c7c1


Revision             Result                  N
chromium@443061      53.9856 +- 1.76942      6      good
chromium@443138      54.7046 +- 3.12623      6      good
chromium@443177      55.2174 +- 2.99911      6      good
chromium@443196      47.1816 +- 2.32565      6      bad
chromium@443215      47.4127 +- 1.86312      6      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests blink_perf.parser

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

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


| 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 Tests>AutoBisect.  Thank you!

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

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

Suspected Commit
  Author : keishi
  Commit : 51ed0d54153a164e68155447fcd1cfcb393f1870
  Date   : Thu Jan 12 10:04:46 2017
  Subject: Add renderer memory metrics

Bisect Details
  Configuration: android_nexus9_perf_bisect
  Benchmark    : blink_perf.parser
  Metric       : iframe-append-remove/iframe-append-remove
  Change       : 12.83% | 53.8921994842 -> 46.9786417745

Revision             Result                  N
chromium@443061      53.8922 +- 1.35306      6      good
chromium@443138      54.5057 +- 2.99194      6      good
chromium@443177      52.7485 +- 1.75696      6      good
chromium@443187      53.7852 +- 2.91456      5      good
chromium@443192      53.3138 +- 1.76989      6      good
chromium@443194      53.9003 +- 2.01025      6      good
chromium@443195      47.7045 +- 2.06334      6      bad       <--
chromium@443196      47.2166 +- 1.9132       6      bad
chromium@443215      46.9786 +- 1.4043       6      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests blink_perf.parser

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

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


| 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 Tests>AutoBisect.  Thank you!

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

=== BISECT JOB RESULTS ===
Perf regression found but unable to narrow commit range

Bisect Details
  Configuration: android_nexus9_perf_bisect
  Benchmark    : blink_perf.parser
  Metric       : iframe-append-remove/iframe-append-remove

Suspected Commit Range
  19 commits in range
  https://chromium.googlesource.com/chromium/src/+log/0635307354bc4b946cb6bf7855a9c133862f02e8..0deb194b2774d9a68a7fcba1d4fe17477767c7c1


Revision             Result                  N
chromium@443061      53.9856 +- 1.76942      6      good
chromium@443138      54.7046 +- 3.12623      6      good
chromium@443177      55.2174 +- 2.99911      6      good
chromium@443196      47.1816 +- 2.32565      6      bad
chromium@443215      47.4127 +- 1.86312      6      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests blink_perf.parser

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

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


| 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!