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

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


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

android-nexus5
android-nexus6

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

=== BISECT JOB RESULTS ===
Perf regression found but unable to narrow commit range

Build failures prevented the bisect from narrowing the range further.


Bisect Details
  Configuration: android_nexus5_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:renderer_processes:reported_by_chrome:v8:heap:effective_size_avg/load_news/load_news_qq
  Change       : 6.05% | 2321650.28571 -> 2462158.85714

Suspected Commit Range
  6 commits in range
  https://chromium.googlesource.com/chromium/src/+log/96381699b93319e8eb824bb506b44572f5c046e9..903fd6842f256f39a5ecba231ade9551b16107a8


Revision             Result                  N
chromium@527408      2321650 +- 46184.4      21       good
chromium@527439      2319367 +- 42532.7      14       good
chromium@527442      2320025 +- 47752.5      21       good
chromium@527444      2320700 +- 23118.0      9        good
chromium@527445      ---                     ---      build failure
chromium@527446      ---                     ---      build failure
chromium@527447      ---                     ---      build failure
chromium@527448      ---                     ---      build failure
chromium@527449      ---                     ---      build failure
chromium@527450      2326390 +- 1932.41      21       bad
chromium@527455      2325673 +- 28029.2      14       bad
chromium@527470      2462159 +- 368572       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=load.news.qq 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/8957877894235264576


For feedback, file a bug with component Speed>Bisection