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

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


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

android-nexus5X
android-nexus7v2

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

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

Suspected Commit
  Author : Eric Seckler
  Commit : 1b697fc546af51e355c458bc4e10f821a1c8d551
  Date   : Sun Sep 24 07:41:53 2017
  Subject: [viz] Ensure that ClientLTFS acknowledges racy BeginFrames.

Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : scheduler.tough_scheduling_cases
  Metric       : mean_main_thread_scroll_latency/sync_scroll_offset.html
  Change       : 78.12% | 18.2333333333 -> 32.4778333333

Revision             Result                   N
chromium@503949      18.2333 +- 0.761489      6      good
chromium@503951      18.278 +- 0.604867       6      good
chromium@503952      32.3975 +- 1.58073       6      bad       <--
chromium@503953      32.4778 +- 2.07512       6      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=sync.scroll.offset.html scheduler.tough_scheduling_cases

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

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


For feedback, file a bug with component Speed>Bisection