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

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


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

chromium-rel-win7-x64-dual

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

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

Hi mark@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 : mark
  Commit : d0b0e164df66904125ecdcf3473212a1d97a11ce
  Date   : Thu Feb 23 16:11:02 2017
  Subject: Update Crashpad to 4a2043ea65e2641ef1a921801c0aaa15ada02fc7

Bisect Details
  Configuration: win_x64_perf_bisect
  Benchmark    : startup.warm.blank_page
  Metric       : first_non_empty_paint_time/first_non_empty_paint_time
  Change       : 4.25% | 158.476190476 -> 165.214285714

Revision             Result                  N
chromium@452444      158.476 +- 132.64       21      good
chromium@452478      150.444 +- 23.2857      9       good
chromium@452495      153.714 +- 68.1679      14      good
chromium@452503      150.222 +- 24.6892      9       good
chromium@452507      160.0 +- 174.763        14      good
chromium@452509      163.222 +- 112.461      9       good
chromium@452510      175.571 +- 142.223      14      bad       <--
chromium@452511      165.214 +- 18.1757      14      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release_x64 --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/8985649527910829568

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


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

https://chromium.googlesource.com/chromium/src/+/d0b0e164df66904125ecdcf3473212a1d97a11ce

None of the stuff in that roll range is in Chrome’s startup path.

Yeah, this bisect is bad, it recovers in the very next CL. It's hard to use the ref build as that's so noisy, but it looks like the ref builds are also regressing, so sorry about the noise. Won'tfix.