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

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


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

Android Nexus6 WebView Perf

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

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/1510ae16e40000

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

gpu: Fix raster implementation error for no flush result available query by khushalsagar@chromium.org
https://chromium.googlesource.com/chromium/src/+/da82bcce69bf5384435976a1945c9cb3270c5abb
queueing_durations: 0.2259 → 0.4711 (+0.2453)

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

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

Things improved with this change: https://chromium.googlesource.com/chromium/src/+/cd8fbb77cfa164eef66378204a588443af9bb875, because it added additional flushing and the raster thread being blocked on that flush finishing which the change above fixed. So things are back to where they were before.

 Issue 898895  has been merged into this issue.

 Issue 898891  has been merged into this issue.