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

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


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

chromium-rel-mac11-air

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

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

Bisect Details
  Configuration: mac_air_perf_bisect
  Benchmark    : blink_perf.dom
  Metric       : delete-in-password-field/delete-in-password-field

Revision             Result                 N
chromium@493996      37.838 +- 3.668        21      good
chromium@494001      38.875 +- 9.37988      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 blink_perf.dom

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

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


For feedback, file a bug with component Speed>Bisection

Bisect can't repro. This looks like it's bimodal and went from mostly low to mostly high. Only on one device. WontFix-ing.