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

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


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

Android Nexus5 Perf

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

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

Revert "Disable GPU clip masks" by ccameron@google.com
https://skia.googlesource.com/skia/+/e2da5f90acf76beefe7dec76a99fc1cb5b0c249d
596.2 → 1171 (+574.8)

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

I think auto-bug assignment failed here because the blame was an @google.com address.

Chris could you take a look?  Looks like a significant regression in N6 WebView's compositing time.

I'm realizing now that ccameron@ only reverted the change.  Adding original author and folks to check.  Did reverting this change possibly mix poorly with other changes?

My revert has been reverted (IIUC).

This issue is marked as a release blocker with no OS labels associated. Please add an appropriate OS label.

All release blocking issues should have OS labels associated to it, so that the issue can tracked and promptly verified, once it gets fixed.

Thanks for your time! To disable nags, add the Disable-Nags label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

[Auto-generated comment by a script] We noticed that this issue is targeted for M-70; it appears the fix may have landed after branch point, meaning a merge might be required. Please confirm if a merge is required here - if so add Merge-Request-70 label, otherwise remove Merge-TBD label. Thanks.