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

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


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

chromium-rel-win7-gpu-ati

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

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

Bisect Details
  Configuration: winx64ati_perf_bisect
  Benchmark    : smoothness.gpu_rasterization.tough_path_rendering_cases
  Metric       : frame_times/GUIMark Vector Chart Test

Revision             Result                   N
chromium@491765      16.7295 +- 0.25686       21      good
chromium@491832      16.7267 +- 0.348384      21      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=GUIMark.Vector.Chart.Test smoothness.gpu_rasterization.tough_path_rendering_cases

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

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


For feedback, file a bug with component Speed>Bisection

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

Re-kicking bisect on a wider range.

=== 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: winx64ati_perf_bisect
  Benchmark    : smoothness.gpu_rasterization.tough_path_rendering_cases
  Metric       : frame_times/GUIMark Vector Chart Test
  Change       : 0.89% | 16.8130967378 -> 16.9633914217

Revision             Result                   N
chromium@491609      16.8131 +- 0.41643       9       good
chromium@491765      16.7177 +- 0.254876      6       good
chromium@491843      16.7553 +- 0.241006      6       good
chromium@491863      16.7654 +- 0.244737      9       good
chromium@491873      16.6621 +- 0.178207      6       good
chromium@491874      16.9028 +- 0.123791      6       bad       <--
chromium@491875      16.945 +- 0.134065       6       bad
chromium@491876      16.9283 +- 0.14724       6       bad
chromium@491878      16.9402 +- 0.145699      6       bad
chromium@491882      16.9266 +- 0.13804       6       bad
chromium@491920      16.9109 +- 0.223285      14      bad
chromium@492231      16.9634 +- 0.118918      9       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=GUIMark.Vector.Chart.Test smoothness.gpu_rasterization.tough_path_rendering_cases

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

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


For feedback, file a bug with component Speed>Bisection