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

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


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

chromium-rel-mac11
chromium-rel-mac11-air
chromium-rel-mac11-pro
chromium-rel-win7-dual
chromium-rel-win7-x64-dual
chromium-rel-win8-dual

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

=== BISECT JOB RESULTS ===
Bisect was unable to run to completion

Please try rerunning the bisect.


If failures persist contact the team (see below) and report the error.


Bisect Details
  Configuration: win_8_perf_bisect
  Benchmark    : loading.desktop
  Metric       : timeToFirstContentfulPaint_avg/pcv1-warm/yahoo.co.jp
  Change       : 267.40% | 179.288666666 -> 658.705000003

Revision                                 Result                  N
chromium@500296                          179.289 +- 120.009      6      good
chromium@500327                          160.169 +- 97.9964      6      good
chromium@500342                          152.086 +- 32.1769      6      good
chromium@500344                          149.369 +- 30.8769      9      good
chromium@500344,catapult@724bb776bc      628.181 +- 605.043      6      bad
chromium@500344,catapult@80c47581b1      575.849 +- 541.183      6      bad
chromium@500344,catapult@4f611510b9      517.651 +- 501.635      6      bad
chromium@500344,catapult@442f46edf7      416.979 +- 667.157      6      bad
chromium@500345                          472.465 +- 777.057      6      bad
chromium@500346                          462.802 +- 890.178      9      bad
chromium@500350                          519.015 +- 506.458      6      bad
chromium@500357                          658.705 +- 339.602      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 --story-filter=yahoo.co.jp loading.desktop

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

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


For feedback, file a bug with component Speed>Bisection

Bisect succeed but somehow didn't report to the bug:


Suspected Commit
  Author : xunjieli
  Commit : 724bb776bcdea642a5bc9cc20fe14bb0282b4900
  Date   : Wed Sep 06 14:29:20 2017
  Subject: [Telemetry] Use --ignore-certificate-errors-spki-list to bypass cert errors

Bisect Details
  Configuration: win_8_perf_bisect
  Benchmark    : loading.desktop
  Metric       : timeToFirstContentfulPaint_avg/pcv1-warm/yahoo.co.jp
  Change       : 267.40% | 179.288666666 -> 658.705000003

Revision                                 Result                  N
chromium@500296                          179.289 +- 120.009      6      good
chromium@500327                          160.169 +- 97.9964      6      good
chromium@500342                          152.086 +- 32.1769      6      good
chromium@500344                          149.369 +- 30.8769      9      good
chromium@500344,catapult@c5a474f50f      152.18 +- 44.5562       9      good
chromium@500344,catapult@724bb776bc      614.641 +- 642.155      9      bad       <--
chromium@500344,catapult@80c47581b1      575.849 +- 541.183      6      bad
chromium@500344,catapult@4f611510b9      517.651 +- 501.635      6      bad
chromium@500344,catapult@442f46edf7      416.979 +- 667.157      6      bad
chromium@500345                          472.465 +- 777.057      6      bad
chromium@500346                          462.802 +- 890.178      9      bad
chromium@500350                          519.015 +- 506.458      6      bad
chromium@500357                          658.705 +- 339.602      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 --story-filter=yahoo.co.jp loading.desktop

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

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


For feedback, file a bug with component Speed>Bisection