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

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


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

perf-go-phone-1024

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

=== 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:system_memory:private_dirty_size_avg/browse_news/browse_news_washingtonpost
  Change       : 1.59% | 48761197.5238 -> 49535731.619

Revision                       Result                   N
android-chrome@1f72ccdb5f      48761198 +- 1441726      21      good
android-chrome@1f580f89fc      49535732 +- 311090       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=browse.news.washingtonpost 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/8945111151832455376


For feedback, file a bug with component Speed>Bisection