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

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


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

Android Nexus5X WebView Perf
android-nexus5x-perf

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

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/163673c0e40000

📍 Found significant differences after each of 3 commits.
https://pinpoint-dot-chromeperf.appspot.com/job/163673c0e40000

Canvas/WebGL: Defer commits to limit queued frames. by ericrk@chromium.org
https://chromium.googlesource.com/chromium/src/+/0dd63a3394566a94619974f91ce14f8d7680512c
33.46 → No values

aw: ReturnedResourceAvailable by boliu@chromium.org
https://chromium.googlesource.com/chromium/src/+/0d8d0e26871adce7024452945a9aec30ac18989c
No values → 48.18

[DevTools] Do not interrupt worker for most of the debugger tasks by dgozman@chromium.org
https://chromium.googlesource.com/chromium/src/+/3384067b2b1e7cc89cc5311d8d3e4b36da10c6ed
48.24 → 49 (+0.7611)

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

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

I think this one was already fixed by the revert [1]. Over to Sunny to confirm.

[1] https://chromium-review.googlesource.com/c/chromium/src/+/1211664

Yes, the above CL was reverted, and graphs seem to have recovered.