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

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


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

android-nexus5
android-nexus5X
android-one
android-webview-nexus5X
chromium-rel-mac12

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

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

Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:skia:effective_size_avg/browse_media/browse_media_youtube

Revision             Result                 N
chromium@524760      422852 +- 4011.14      21      good
chromium@524876      422886 +- 3989.4       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-chromium --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/8959561365349168640


For feedback, file a bug with component Speed>Bisection

Another memory regression which doesn't repro in bisect, and comes back down later.