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

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


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

android-nexus5

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

=== BISECT JOB RESULTS ===
Perf regression found but unable to continue

Bisect was stopped because a commit couldn't be classified as either
good or bad.


Bisect Details
  Configuration: android_nexus5_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:v8:effective_size_avg/load_search/load_search_google

Revision             Result                  N
chromium@488740      4540309 +- 56541.7      21      good
chromium@488755      4757528 +- 1404423      21      good
chromium@488763      4831782 +- 1454932      21      unknown
chromium@488770      4961833 +- 1295232      21      bad
chromium@488800      4948038 +- 987526       14      bad
chromium@488859      4987603 +- 1027200      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/8973104474064162112


For feedback, file a bug with component Speed>Bisection

This only happened on one device, no ref build.