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

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


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

android-nexus5X

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

=== BISECT JOB RESULTS ===
Perf regression found but unable to continue

Bisect was stopped because a commit couldn't be classified as either
good or bad.


Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:malloc:effective_size_avg/background_social/background_social_facebook

Revision             Result                   N
chromium@518766      41505115 +- 1402600      21      good
chromium@518782      41266136 +- 1529805      21      unknown
chromium@518798      41166596 +- 1622288      21      bad
chromium@518836      41266429 +- 1150021      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=background.social.facebook 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/8961038359362650400


For feedback, file a bug with component Speed>Bisection