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

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


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

android-nexus5
android-nexus5X
android-one

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

=== 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:malloc:effective_size_avg/background_news/background_news_nytimes

Revision             Result                   N
chromium@486056      52918477 +- 2114116      21      good
chromium@486073      52926885 +- 1901860      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.news.nytimes 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/8973425039479268848


For feedback, file a bug with component Speed>Bisection

This is pretty old and bisect can't repro.