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

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


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

chromium-rel-win10
chromium-rel-win7-dual
chromium-rel-win7-gpu-ati
chromium-rel-win7-gpu-intel
chromium-rel-win7-gpu-nvidia
chromium-rel-win7-x64-dual
chromium-rel-win8-dual
linux-release
win-high-dpi

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

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

Hi krb@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 : Kevin Bailey
  Commit : 3cda6c9c7ee5274ea800bce409691a15a949fc2c
  Date   : Thu Aug 03 23:20:18 2017
  Subject: [omnibox] Select-all after revert-all, in more cases

Bisect Details
  Configuration: winx64nvidia_perf_bisect
  Benchmark    : smoothness.tough_animation_cases
  Metric       : frame_times/overlay_background_color_css_transitions.html
  Change       : 54.95% | 187.64585549 -> 290.752704613

Revision             Result                  N
chromium@491872      187.646 +- 10.1587      6      good
chromium@491873      191.956 +- 6.96093      6      good
chromium@491874      287.904 +- 20.7321      6      bad       <--
chromium@491875      290.196 +- 17.7443      6      bad
chromium@491878      293.06 +- 23.3202       6      bad
chromium@491883      289.091 +- 24.2558      6      bad
chromium@491893      287.548 +- 35.373       6      bad
chromium@491913      286.677 +- 17.1371      6      bad
chromium@491953      290.753 +- 42.6334      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=overlay.background.color.css.transitions.html smoothness.tough_animation_cases

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

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


For feedback, file a bug with component Speed>Bisection

See 739303 and 741714. This is actually caused by an error in measurement, something like aliasing.