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

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


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

android-nexus5
android-one

Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8958520966372084000

=== BISECT JOB RESULTS ===
NO Perf regression found

Bisect Details
  Configuration: android_one_perf_bisect
  Benchmark    : memory.top_10_mobile
  Metric       : memory:chrome:all_processes:reported_by_os:system_memory:native_heap:proportional_resident_size_avg/foreground/https_m_facebook_com_rihanna

Revision             Result                   N
chromium@525283      19092683 +- 2127040      21      good
chromium@525321      19018370 +- 1578453      21      bad

Please refer to the following doc on diagnosing memory regressions:
  https://chromium.googlesource.com/chromium/src/+/master/docs/memory-infra/memory_benchmarks.md

To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=https.m.facebook.com.rihanna memory.top_10_mobile

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8958520966372084000


For feedback, file a bug with component Speed>Bisection

Looks like the metric subsequently recovered.