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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg-OvXsgsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg-MH-uQsM


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

android-nexus5

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

=== 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    : memory.top_10_mobile_stress
  Metric       : memory:chrome:all_processes:reported_by_chrome:cc:effective_size_avg/foreground/http_search_yahoo_com_search__ylt_p_google
  Change       : 5.13% | 19218548.0 -> 20203505.7143

Suspected Commit Range
  4 commits in range
  https://chromium.googlesource.com/chromium/src/+log/9cdf01f7131fa57830221af1156b1a3ca1e11578..3d2b854663e325f0618ff313a4c58ff20e959891


Revision             Result                   N
chromium@451379      19218548 +- 3495499      14       good
chromium@451393      19221829 +- 3486617      14       good
chromium@451395      19223603 +- 3521443      14       good
chromium@451396      ---                      ---      build failure
chromium@451397      ---                      ---      build failure
chromium@451398      ---                      ---      build failure
chromium@451399      20688557 +- 1838191      9        bad
chromium@451401      20286239 +- 2622703      21       bad
chromium@451407      20203506 +- 2515555      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 memory.top_10_mobile_stress

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

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


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

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

Trying a narrow bisect on that 451395-451399 range.

=== 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    : memory.top_10_mobile_stress
  Metric       : memory:chrome:all_processes:reported_by_os:gpu_memory:proportional_resident_size_avg/foreground/http_search_yahoo_com_search__ylt_p_google


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 memory.top_10_mobile_stress

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

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


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

=== BISECT JOB RESULTS ===
Bisect failed for unknown reasons

Please contact the team (see below) and report the error.


Bisect Details
  Configuration: android_nexus5_perf_bisect
  Benchmark    : memory.top_10_mobile_stress
  Metric       : memory:chrome:all_processes:reported_by_chrome:cc:effective_size_avg/foreground/http_search_yahoo_com_search__ylt_p_google


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 memory.top_10_mobile_stress

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

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


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