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

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


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

android-webview-nexus5X

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

📍 Found a significant difference after 1 commit.
https://chromeperf.appspot.com/job/16ff35d7840000

aw: Make DrawFunctor event toplevel by boliu@chromium.org
https://chromium.googlesource.com/chromium/src/+/3f2e2f3ad18154cc118413b74e5777c686a5c5c2

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

Android webview one expected (dup of 813972). But there's also a mac one?

-> vmiura, I dunno how to perf things like this. Can you handle this like the other bug?

 Issue 815321  has been merged into this issue.

chromium-rel-mac11-pro regression re-triaged to  Issue 815322 .
fboliu: The way to do it is, From the link to the "Original alerts at time of bug-filing" above, you can see all of the regressions tagged with this Issue number.

Steps:
 1) Expand all alerts in the group (click the square on the left which shows the 
# of grouped alerts).
 2) Select alerts you want to re-triage and assign a different bug via the "Triage" button.

cool, thanks