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

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


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

chromium-rel-mac12

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

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

The bisect was able to narrow the range, you can try running with:
  good_revision: 51ce668aebf388516f2349a0b55bc622c14e3f4c
  bad_revision : db210de154551f5b47357592bab4612303b7a381

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


Bisect Details
  Configuration: mac_10_12_perf_bisect
  Benchmark    : startup.cold.blank_page
  Metric       : open_tabs_time/open_tabs_time
  Change       : 48.01% | 301.0 -> 156.5

Revision             Result                  N
chromium@463741      301.0 +- 51.4782        6      good
chromium@463840      297.5 +- 49.371         6      good
chromium@463844      303.5 +- 37.0338        6      good
chromium@463846      155.667 +- 35.0904      6      bad
chromium@463847      154.167 +- 42.1288      6      bad
chromium@463853      150.667 +- 43.9014      6      bad
chromium@463865      147.833 +- 41.7473      6      bad
chromium@463889      149.333 +- 42.7005      6      bad
chromium@463938      156.5 +- 44.0625        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 startup.cold.blank_page

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

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


| 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/8981206328490605024

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

Hi samans@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 : samans
  Commit : 2040988b1345e6ce738bd03ab7ccd5f4b73a956b
  Date   : Tue Apr 11 23:58:35 2017
  Subject: Use MojoCompositorFrameSink in RendererCompositorFrameSink

Bisect Details
  Configuration: mac_10_12_perf_bisect
  Benchmark    : startup.cold.blank_page
  Metric       : open_tabs_time/open_tabs_time
  Change       : 55.43% | 319.0 -> 142.166666667

Revision             Result                  N
chromium@463741      319.0 +- 54.9545        6      good
chromium@463840      315.833 +- 38.8694      6      good
chromium@463844      303.167 +- 40.9492      6      good
chromium@463845      141.5 +- 24.5255        6      bad       <--
chromium@463846      148.167 +- 39.9354      6      bad
chromium@463847      173.5 +- 34.8353        6      bad
chromium@463853      157.0 +- 42.8019        6      bad
chromium@463865      157.833 +- 48.3201      6      bad
chromium@463889      155.333 +- 50.0733      6      bad
chromium@463938      142.167 +- 46.8063      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 startup.cold.blank_page

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

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


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