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

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


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

android-nexus5x-perf

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

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

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

gpu: Expand oopr workaround to fallback to ES2 to all android versions. by khushalsagar@chromium.org
https://chromium.googlesource.com/chromium/src/+/2b62fe723102af55ae3c3508d013655647af440b
0.4217 → 1.395 (+0.9734)

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

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

The test which regressed is web_animation_value_type_path, I'm going to guess the fallback to ES2 changed the path rendering option in skia.

This is still a WontFix. Its a temporary workaround for a GPU crash and it brings us back to the performance we had with GPU raster.

 Issue 887289  has been merged into this issue.