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

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


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

android-nexus7v2

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

=== 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_nexus7_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:malloc:effective_size_avg/load_news/load_news_reddit
  Change       : 0.42% | 19487349.1429 -> 19568802.2857

Suspected Commit Range
  2 commits in range
  https://chromium.googlesource.com/chromium/src/+log/4e647815da3389ad12b9c376ba9786ab9758cab0..83c49f99a4076209023e0deeb9f07a9c623f3719


Revision             Result                  N
chromium@487872      19487349 +- 332710      14       good
chromium@487921      19472917 +- 266168      14       good
chromium@487928      19443193 +- 264985      6        good
chromium@487931      19483197 +- 484039      14       good
chromium@487932      19495421 +- 363390      14       good
chromium@487933      ---                     ---      build failure
chromium@487934      19584255 +- 367550      21       bad
chromium@487946      19561276 +- 289731      14       bad
chromium@487970      19592376 +- 175357      9        bad
chromium@488067      19568802 +- 252002      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.reddit 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/8973190893287203872


For feedback, file a bug with component Speed>Bisection

This is pretty noisy, bisect only reproduced an 80kib regression and couldn't narrow further.