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

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


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

Win 7 Perf

rendering.desktop - Benchmark documentation link:
  https://bit.ly/rendering-benchmarks

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/14c37be6140000

📍 Found significant differences after each of 2 commits.
https://pinpoint-dot-chromeperf.appspot.com/job/14c37be6140000

Fixed fling regression from registering observer on GSB instead of GFS. by sahel@chromium.org
https://chromium.googlesource.com/chromium/src/+/0b48b62c4392e7cd594d9fbe8684e93abc72aa1b
thread_total_all_cpu_time_per_frame: 9.914 → No values

Roll src/third_party/catapult f04a3a61ad90..5d5091665700 (1 commits) by chromium-autoroll@skia-public.iam.gserviceaccount.com
https://chromium.googlesource.com/chromium/src/+/04baa857df8e2142aa06d5414656df7056feb52b
thread_total_all_cpu_time_per_frame: No values → 10.1

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

Benchmark documentation link:
  https://bit.ly/rendering-benchmarks