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

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


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

android-nexus5

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

=== 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_os:system_memory:native_heap:proportional_resident_size_avg/load_search/load_search_google
  Change       : 2.23% | 21267351.4286 -> 21698382.2857

Suspected Commit Range
  15 commits in range
  https://chromium.googlesource.com/chromium/src/+log/974e0b5564781b8c620acc6efa78e0566f2bf397..b15287cba7207048d9023ef3bf8d4a2574b0a04d


Revision             Result                   N
chromium@488740      21267351 +- 247148       14       good
chromium@488755      21537468 +- 1173508      14       good
chromium@488756      ---                      ---      build failure
---                  ---                      ---      too many build failures to list
chromium@488769      ---                      ---      build failure
chromium@488770      21702259 +- 1161348      14       bad
chromium@488799      21711646 +- 1317550      21       bad
chromium@488859      21698382 +- 1049441      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.search.google 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/8973104445566362912


For feedback, file a bug with component Speed>Bisection

This metric appears to have recovered and subsequently regressed again.