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

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


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

win-high-dpi

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

=== Auto-CCing suspected CL author findit-for-me@appspot.gserviceaccount.com ===

Hi findit-for-me@appspot.gserviceaccount.com, 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 : Findit
  Commit : 7d32a0994f53fed87e6b290bd7cd7a9121b5a0bd
  Date   : Mon Jul 24 17:18:24 2017
  Subject: Revert "[Autofill] Compare with last four for masked card when determining type"

Bisect Details
  Configuration: winx64_high_dpi_perf_bisect
  Benchmark    : media.tough_video_cases_tbmv2
  Metric       : video_animation:power_avg/video.html?src_tulip2.mp4
  Change       : 38.02% | 0.646530777598 -> 0.400714913505

Revision             Result                      N
chromium@488994      0.646531 +- 0.949716        6      good
chromium@488995      0.36317 +- 0.00659659       6      bad       <--
chromium@488996      0.364992 +- 0.0151231       6      bad
chromium@488997      0.366648 +- 0.00906102      6      bad
chromium@488999      0.364161 +- 0.00989079      6      bad
chromium@489003      0.380203 +- 0.0471863       6      bad
chromium@489011      0.377022 +- 0.0145576       6      bad
chromium@489027      0.396812 +- 0.0852977       9      bad
chromium@489060      0.386629 +- 0.025702        6      bad
chromium@489125      0.400715 +- 0.0163024       6      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=video.html.src.tulip2.mp4 media.tough_video_cases_tbmv2

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

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


For feedback, file a bug with component Speed>Bisection

+sullivan@, seems like we need more complex logic for assigning bug for changes submitted by bots.

Looks like the regression has fixed itself.