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

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


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

android-nexus5X
android-one

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

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

Please try rerunning the bisect.


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


Bisect Details
  Configuration: android_one_perf_bisect
  Benchmark    : smoothness.gpu_rasterization.top_25_smooth
  Metric       : mean_input_event_latency/Docs  (1 open document tab)

Revision             Result                  N
chromium@499266      19.1299 +- 1.97523      14      good
chromium@502500      108.731 +- 27.5463      14      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=Docs...1.open.document.tab. smoothness.gpu_rasterization.top_25_smooth

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

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


For feedback, file a bug with component Speed>Bisection

Bisect unable to find culprit, this regression exists in stable. Ignoring.