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

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


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

linux-release

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

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

Bisect Details
  Configuration: linux_perf_bisect
  Benchmark    : startup.warm.blank_page
  Metric       : open_tabs_time/open_tabs_time

Revision             Result                  N
chromium@472338      23.5238 +- 10.5469      21      good
chromium@472431      25.0 +- 11.3137         21      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=2 --also-run-disabled-tests startup.warm.blank_page

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

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


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

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

Build failures prevented the bisect from narrowing the range further.


Bisect Details
  Configuration: linux_perf_bisect
  Benchmark    : startup.warm.blank_page
  Metric       : open_tabs_time/open_tabs_time
  Change       : 12.50% | 22.8571428571 -> 25.7142857143

Suspected Commit Range
  2 commits in range
  https://chromium.googlesource.com/chromium/src/+log/9e3c1f13fb959c98bdb6aa91aa510e51e635eac7..fbec38011870753cffb3cb2ff98aa0c00c63b25c


Revision             Result                  N
chromium@472338      22.8571 +- 10.8891      21       good
chromium@472383      22.5238 +- 8.44027      21       good
chromium@472409      22.0714 +- 8.42191      14       good
chromium@472411      22.4762 +- 13.388       21       good
chromium@472412      ---                     ---      build failure
chromium@472413      25.2143 +- 9.50564      14       bad
chromium@472415      24.5 +- 7.44983         14       bad
chromium@472420      24.8333 +- 3.2914       6        bad
chromium@472431      25.7143 +- 12.3635      14       bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=2 --also-run-disabled-tests startup.warm.blank_page

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

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


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

This alert was found before M-60 branched. Closing as WontFix as this is believed to either be invalid or non-reproducible.