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

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


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

perf-go-phone-512

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

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

Bisect Details
  Configuration: go-phone-512-perf-bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_os:gpu_memory:proportional_resident_size_avg/load_tools/load_tools_stackoverflow
  Change       : 0.32% | 4434600.66667 -> 4448774.14286

Revision                       Result                  N
android-chrome@b425a64a09      4434601 +- 79628.3      21      good
android-chrome@fc263d8616      4448774 +- 94134.2      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-chrome --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=load.tools.stackoverflow system_health.memory_mobile

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

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


For feedback, file a bug with component Speed>Bisection