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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgvN6b6QoM


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

android-nexus5X

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

=== BISECT JOB RESULTS ===
NO Perf regression found

Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_os:system_memory:java_heap:proportional_resident_size_avg/background_search/background_search_google

Revision             Result                  N
chromium@461329      4600247 +- 79445.1      21      good
chromium@461337      4593371 +- 79768.8      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=background.search.google system_health.memory_mobile

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8982929717183061024

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5237551817818112


| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Speed>Bisection.  Thank you!

Memory usage is gradually increasing, but it's not clear there is any particular change associated with it. Perhaps something in the lab environment?

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