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

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


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

perf-go-phone-1024

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

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

Bisect Details
  Configuration: go-phone-1024-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_weather
  Change       : 3.82% | 20872579.4286 -> 20074444.5714

Revision                       Result                   N
android-chrome@061a8220c9      20872579 +- 2474387      21      good
android-chrome@724ac867b5      20074445 +- 2126340      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.weather 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/8947464689688542656


For feedback, file a bug with component Speed>Bisection

This recovered.