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

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


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

chromium-rel-mac11-pro

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

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

Bisect Details
  Configuration: mac_pro_perf_bisect
  Benchmark    : smoothness.top_25_smooth
  Metric       : first_gesture_scroll_update_latency/Facebook

Revision             Result                   N
chromium@495096      3.15538 +- 0.498607      21      good
chromium@495147      3.13752 +- 0.583897      21      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=Facebook smoothness.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/8970007078944819136


For feedback, file a bug with component Speed>Bisection

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/128f1e09780000

Kicking off another bisect on the later regression, which seems much more severe.

📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/128f1e09780000

Wheel scroll latching and async wheel events flags enabled in testing config.
By sahel@chromium.org · Fri Aug 25 19:16:21 2017
chromium @ f53825a1fb92e74b9a889b9501243e03de57094d

Understanding performance regressions:
  http://g.co/ChromePerformanceRegressions

Bisect unable to find culprit. This exists in stable. Ignoring.