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

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


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

health-plan-clankium-low-end-phone
health-plan-webview-phone
integration-android-low-end-phone
perf-go-phone-1024
perf-go-phone-512
perf-go-webview-phone
perf-monochrome-n-phone

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

=== 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:gpu:effective_size_avg/browse_social/browse_social_facebook
  Change       : 0.80% | 4706728.7619 -> 4744543.42857

Revision                       Result                 N
android-chrome@801e0585fe      4706729 +- 217229      21      good
android-chrome@6a69fc540e      4744543 +- 150570      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.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/8940834160572551136


For feedback, file a bug with component Speed>Bisection

No data is available.