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

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


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

Android Nexus5 Perf
Win 7 Nvidia GPU Perf

memory.desktop - Benchmark documentation link:
  None

system_health.memory_mobile - Benchmark documentation link:
  https://bit.ly/system-health-benchmarks

system_health.memory_desktop - Benchmark documentation link:
  https://bit.ly/system-health-benchmarks

memory.top_10_mobile - Benchmark documentation link:
  None

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

📍 Found significant differences after each of 2 commits.
https://pinpoint-dot-chromeperf.appspot.com/job/143b0609e40000

Saner fallback path when RasterBuffer failed to create a GPU resource by piman@chromium.org
https://chromium.googlesource.com/chromium/src/+/6363d820305bcf1d3fbeb9d031bb929e062a7de5
memory:chrome:all_processes:reported_by_chrome:skia:effective_size: 4.793e+06 → 4.793e+06 (+206.4)

Roll src/third_party/skia c09dc8ac723f..71652e2a09b7 (3 commits) by chromium-autoroll@skia-public.iam.gserviceaccount.com
https://chromium.googlesource.com/chromium/src/+/bb9b07495bd7d17f632c21cdfe5018fe7bc9f813
memory:chrome:all_processes:reported_by_chrome:skia:effective_size: 4.793e+06 → 7.239e+06 (+2.447e+06)

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

Benchmark documentation link:
  None

Assigned, but no owner or component? Please find a component and/or owner