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

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


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

android-nexus5x-perf

media.mobile - Benchmark documentation link:
  None

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

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

Android OOP-D: Enable OOP-D for Android Waterfall by ericrk@chromium.org
https://chromium.googlesource.com/chromium/src/+/86da5de5d854b46ef4e85bbef645a1c0866ed13b
5.471e+06 → 6.195e+06 (+7.247e+05)

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

 Issue 879195  has been merged into this issue.

 Issue 879196  has been merged into this issue.

 Issue 879343  has been merged into this issue.

 Issue 879332  has been merged into this issue.

 Issue 879330  has been merged into this issue.

 Issue 879598  has been merged into this issue.

 Issue 879595  has been merged into this issue.

 Issue 879187  has been merged into this issue.

 Issue 879188  has been merged into this issue.

 Issue 879192  has been merged into this issue.

 Issue 879197  has been merged into this issue.

 Issue 879634  has been merged into this issue.

 Issue 879714  has been merged into this issue.

The memory:chrome:all_processes:reported_by_chrome:cc:effective_size_avg/ regressions were reporting issues fixed by kylechar@ in https://chromium-review.googlesource.com/1211955

The memory:chrome:all_processes:reported_by_chrome:gpu:effective_size_avg regressions were a real regression that I fixed here: https://chromium-review.googlesource.com/c/chromium/src/+/1237405

All issues here are recovered.