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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgsM_yuAkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg8NOlsgkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg8OaSvwkM


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

android-nexus5X
chromium-rel-win7-gpu-ati

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

=== 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_chrome:malloc:effective_size_avg/load_search/load_search_taobao

Revision             Result                    N
chromium@446006      124059124 +- 2696102      21      good
chromium@446024      123986430 +- 2779491      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=load.search.taobao system_health.memory_mobile

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

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


| 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 Tests>AutoBisect.  Thank you!

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

=== 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_chrome:malloc:effective_size_avg/load_search/load_search_taobao

Revision             Result                    N
chromium@446006      124028377 +- 2465761      21      good
chromium@446024      124099939 +- 3167252      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=load.search.taobao system_health.memory_mobile

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

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


| 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!

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

This alert was found before M-60 branched. Closing as WontFix as this is believed to either be invalid or non-reproducible.