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

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


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

perf-go-phone-1024

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

=== 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_chrome:java_heap:allocated_objects_size_avg/load_games/load_games_bubbles
  Change       : 18.09% | 4337903.2381 -> 5122472.7619

Revision                       Result                 N
android-chrome@a8d6449870      4337903 +- 971262      21      good
android-chrome@3fea53a776      5122473 +- 137313      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.games.bubbles 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/8947447791769014480


For feedback, file a bug with component Speed>Bisection

Bisect can't repro, looks like a blip?