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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDguKKMvwsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg2NfF-wsM


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

chromium-rel-mac12

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

=== BISECT JOB RESULTS ===
NO Perf regression found

Bisect Details
  Configuration: mac_10_12_perf_bisect
  Benchmark    : startup.cold.blank_page
  Metric       : first_non_empty_paint_time/first_non_empty_paint_time

Revision             Result                  N
chromium@449889      692.429 +- 352.876      21      good
chromium@449893      680.0 +- 249.339        21      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 startup.cold.blank_page

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

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


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

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

=== BISECT JOB RESULTS ===
NO Perf regression found

Bisect Details
  Configuration: mac_10_12_perf_bisect
  Benchmark    : startup.cold.blank_page
  Metric       : first_non_empty_paint_time/first_non_empty_paint_time

Revision             Result                  N
chromium@449500      711.905 +- 382.186      21      good
chromium@450000      704.048 +- 295.667      21      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 startup.cold.blank_page

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

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


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

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

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

=== Auto-CCing suspected CL author rsesek@chromium.org ===

Hi rsesek@chromium.org, the bisect results pointed to your CL, please take a look at the
results.


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

Suspected Commit
  Author : rsesek
  Commit : b663b64c6237463da5417e040681f689a45ce3e1
  Date   : Tue Feb 14 01:47:01 2017
  Subject: [Mac] Do not strip out Headers from KeystoneRegistration.framework.

Bisect Details
  Configuration: mac_10_12_perf_bisect
  Benchmark    : startup.cold.blank_page
  Metric       : first_main_frame_load_time/first_main_frame_load_time
  Change       : 13.84% | 688.0 -> 783.222222222

Revision             Result                  N
chromium@449889      688.0 +- 263.424        14      good
chromium@450192      675.111 +- 109.922      9       good
chromium@450193      665.0 +- 53.3667        6       good
chromium@450194      775.667 +- 121.579      6       bad       <--
chromium@450195      770.444 +- 112.5        9       bad
chromium@450197      767.0 +- 130.599        9       bad
chromium@450202      765.0 +- 120.806        9       bad
chromium@450211      790.0 +- 126.206        6       bad
chromium@450230      790.0 +- 123.507        6       bad
chromium@450268      783.167 +- 142.908      6       bad
chromium@450344      796.833 +- 86.8955      6       bad
chromium@450495      755.786 +- 151.223      14      bad
chromium@451100      783.222 +- 138.714      9       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 startup.cold.blank_page

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

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


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