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

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


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

mac-10_13_laptop_high_end-perf

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

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/14589685e40000

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

gpu: Fix raster implementation error for no flush result available query by khushalsagar@chromium.org
https://chromium.googlesource.com/chromium/src/+/da82bcce69bf5384435976a1945c9cb3270c5abb
thread_total_all_cpu_time_per_frame: 171.1 → 286.3 (+115.2)

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

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

This change fixes an error that was introduced in a previous change. The regression brings us back to where we were before the previous one.