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

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


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

android-nexus5X

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

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

=== BISECT JOB RESULTS ===
Bisect failed unexpectedly

Bisect was aborted with the following:
  Step('Check bisect finished on revision chromium@469837,skia@4c6e4103a2.fetch file 4c6e4103a246c27bdd1302a9c7fba64367758dcc:DEPS') failed with return_code 1


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/load_search/load_search_taobao

Revision                             Result                   N
chromium@469837                      16366763 +- 143546       6      good
chromium@469837,skia@4c6e4103a2      16888491 +- 2530687      6      good
chromium@469838                      19283285 +- 144719       6      bad
chromium@469839                      19460608 +- 133346       6      bad
chromium@469841                      19694933 +- 281239       6      bad
chromium@469844                      19534677 +- 263144       6      bad
chromium@469851                      19345067 +- 159788       6      bad
chromium@469865                      18973525 +- 345677       6      bad
chromium@469893                      18785109 +- 254445       6      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/8980147230391020160

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


| 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/8980095963092831136

=== BISECT JOB RESULTS ===
Bisect failed unexpectedly

Bisect was aborted with the following:
  Step('Check bisect finished on revision chromium@469837,skia@4c6e4103a2.fetch file 4c6e4103a246c27bdd1302a9c7fba64367758dcc:DEPS') failed with return_code 1


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/load_search/load_search_taobao

Revision                             Result                   N
chromium@469837                      16401579 +- 198135       6      good
chromium@469837,skia@4c6e4103a2      16830464 +- 2633882      9      good
chromium@469838                      19289088 +- 81753.4      6      bad
chromium@469839                      19436373 +- 90893.1      6      bad
chromium@469841                      19595947 +- 130813       6      bad
chromium@469844                      19556523 +- 177990       6      bad
chromium@469851                      19410603 +- 164852       6      bad
chromium@469865                      19003221 +- 260082       6      bad
chromium@469893                      18768043 +- 295358       6      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/8980147211032667536

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


| 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/8980092189997977664

=== BISECT JOB RESULTS ===
Bisect failed unexpectedly

Bisect was aborted with the following:
  Step('Check bisect finished on revision chromium@469837,skia@4c6e4103a2.fetch file 4c6e4103a246c27bdd1302a9c7fba64367758dcc:DEPS') failed with return_code 1


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/load_search/load_search_taobao

Revision                             Result                   N
chromium@469837                      16309419 +- 376162       6      good
chromium@469837,skia@4c6e4103a2      17113088 +- 3449638      9      good
chromium@469838                      19287040 +- 167279       6      bad
chromium@469839                      19425792 +- 108474       6      bad
chromium@469841                      19605333 +- 241010       6      bad
chromium@469844                      19460267 +- 204115       6      bad
chromium@469851                      19327317 +- 348974       6      bad
chromium@469865                      19015851 +- 422867       6      bad
chromium@469893                      18813440 +- 227147       6      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/8980095963092831136

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


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

=== BISECT JOB RESULTS ===
Bisect failed unexpectedly

Bisect was aborted with the following:
  Step('Check bisect finished on revision chromium@469837,skia@4c6e4103a2.fetch file 4c6e4103a246c27bdd1302a9c7fba64367758dcc:DEPS') failed with return_code 1


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/load_search/load_search_taobao

Revision                             Result                   N
chromium@469837                      16327851 +- 300496       6      good
chromium@469837,skia@4c6e4103a2      16889685 +- 2558464      6      good
chromium@469838                      19269973 +- 127320       6      bad
chromium@469839                      19436373 +- 115666       6      bad
chromium@469841                      19665067 +- 230286       6      bad
chromium@469844                      19543893 +- 160258       6      bad
chromium@469851                      19372373 +- 156258       6      bad
chromium@469865                      18984448 +- 328957       6      bad
chromium@469893                      18786133 +- 220202       6      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/8980092189997977664

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


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

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