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

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


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

chromium-rel-win7-gpu-intel

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

=== BISECT JOB RESULTS ===
Bisect was unable to run to completion

Error: INFRA_FAILURE

The bisect was able to narrow the range, you can try running with:
  good_revision: c64c683e64cd68f22fcd9472f2adfde10d6b59be
  bad_revision : 75bf68312a3998a396bbc0a44f88e0b62acb17ec

If failures persist contact the team (see below) and report the error.


Bisect Details
  Configuration: winx64intel_perf_bisect
  Benchmark    : smoothness.tough_canvas_cases
  Metric       : frame_times/frame_times

Revision             Result                    N
chromium@484843      22.927 +- 0.656337        6       good
chromium@484952      23.2149 +- 0.511137       6       good
chromium@484980      23.3149 +- 0.380346       3       good
chromium@484987      23.0956 +- 0.0758759      3       good
chromium@484991      23.1898 +- 0.0382245      3       good
chromium@484994      24.4447 +- 0.487535       14      bad
chromium@485007      24.4446 +- 0.567121       14      bad
chromium@485061      23.9043 +- 0.947978       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 smoothness.tough_canvas_cases

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

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


For feedback, file a bug with component Speed>Bisection

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

Looks like tough_canvas_cases_rendering_throughput_bouncing_png_images.html is the page that actually regressed: https://chromeperf.appspot.com/report?sid=ea2f381de05d38b349fd7018516e819934f09c08590dfcea495455e13a140ff2

Kicked off the bisect on that one, and switched the alerting to individual pages, since these summary graphs don't have good signal and don't bisect well.

=== BISECT JOB RESULTS ===
Perf regression found with culprit

Suspected Commit
  Author : Kevin Bailey
  Commit : 5604cb88fc88d2c3b7886702e8253b21ceea600e
  Date   : Fri Jul 07 18:28:44 2017
  Subject: Revert "[omnibox] Select all when we revert all"

Bisect Details
  Configuration: winx64intel_perf_bisect
  Benchmark    : smoothness.tough_canvas_cases
  Metric       : frame_times/tough_canvas_cases_rendering_throughput_bouncing_png_images.html
  Change       : 978.98% | 40.5360952381 -> 459.686533905

Revision             Result                   N
chromium@484843      40.5361 +- 0.600942      7       good
chromium@484952      40.6354 +- 0.450007      3       good
chromium@484980      40.5604 +- 0.889477      5       good
chromium@484987      55.9817 +- 53.1583       4       good
chromium@484991      40.6314 +- 0.468437      4       good
chromium@484992      477.631 +- 223.815       9       bad       <--
chromium@484993      494.203 +- 203.408       9       bad
chromium@484994      460.061 +- 236.445       9       bad
chromium@485007      462.409 +- 294.135       14      bad
chromium@485061      459.687 +- 305.869       14      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=tough.canvas.cases.rendering.throughput.bouncing.png.images.html smoothness.tough_canvas_cases

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

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


For feedback, file a bug with component Speed>Bisection