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

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


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

android-nexus5

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

=== 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:all_processes:reported_by_chrome:malloc:effective_size_avg/load_news/load_news_cnn
  Change       : 1.16% | 24239537.0 -> 24520449.7857

Suspected Commit Range
  7 commits in range
  https://chromium.googlesource.com/chromium/src/+log/e3c9b016e84bb51eb0733a3b256a8aa83cdc9dd1..8a8b48bbb041957b9c6824322ce910536771bf50


Revision             Result                   N
chromium@487872      24239537 +- 643567       14       good
chromium@487929      24331396 +- 1478945      14       good
chromium@487959      24277472 +- 660510       21       good
chromium@487960      ---                      ---      build failure
chromium@487961      ---                      ---      build failure
chromium@487962      ---                      ---      build failure
chromium@487963      ---                      ---      build failure
chromium@487964      ---                      ---      build failure
chromium@487965      ---                      ---      build failure
chromium@487966      24418020 +- 1168658      14       bad
chromium@487972      24638694 +- 837637       6        bad
chromium@487985      24410102 +- 319716       14       bad
chromium@488097      24520450 +- 1406581      14       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.cnn 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/8973190878788060736


For feedback, file a bug with component Speed>Bisection

This is really noisy and there's a lot of build failures and the graph has come back down a bit.