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

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


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

android-nexus7v2

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

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

Bisect Details
  Configuration: android_nexus7_perf_bisect
  Benchmark    : memory.top_10_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:malloc:effective_size_avg/foreground/http_www_baidu_com_s_word_google

Revision             Result                  N
chromium@482795      20891228 +- 554924      21      good
chromium@482883      20916820 +- 460272      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 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/8971643829780535488


For feedback, file a bug with component Speed>Bisection

This is only on one device, which we've since stopped monitoring these tests on, and bisect can't repro.