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

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


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

android-nexus5x-perf

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

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

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

Introduce bundle-specific native libraries by cjgrant@chromium.org
https://chromium.googlesource.com/chromium/src/+/50ab16b8b9eff6611a5b6ec5eade28c54aa7726c
memory:chrome:all_processes:reported_by_chrome:v8:allocated_objects_size: 1.149e+07 → No values

Revert "Introduce bundle-specific native libraries" by oysteine@chromium.org
https://chromium.googlesource.com/chromium/src/+/597c6ab3c70e51e91e2b0114c12d62ad062a0b8d
memory:chrome:all_processes:reported_by_chrome:v8:allocated_objects_size: No values → 1.163e+07

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

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