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

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


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

health-plan-webview-low-end-phone
health-plan-webview-phone
perf-go-phone-512

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

=== 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_chrome:cc:effective_size_avg/browse_media/browse_media_youtube
  Change       : 0.17% | 11679246.1905 -> 11659501.3333

Revision                       Result                  N
android-chrome@8e54c6dbe8      11679246 +- 366800      21      good
android-chrome@4ea344bada      11659501 +- 407387      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.media.youtube 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/8943215560067497536


For feedback, file a bug with component Speed>Bisection