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

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


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

android-one

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

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

Bisect Details
  Configuration: android_one_perf_bisect
  Benchmark    : memory.top_10_mobile_stress
  Metric       : memory:chrome:all_processes:reported_by_chrome:v8:effective_size_avg/foreground/http_yandex_ru_touchsearch_text_science

Revision             Result                 N
chromium@443251      7810933 +- 566495      21      good
chromium@443443      7780828 +- 365685      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=http.yandex.ru.touchsearch.text.science memory.top_10_mobile_stress

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

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


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

Blocking on crbug.com/675639 for no memory.top_10_* repro

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

=== 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_one_perf_bisect
  Benchmark    : memory.top_10_mobile_stress
  Metric       : memory:chrome:all_processes:reported_by_chrome:v8:effective_size_avg/foreground/http_yandex_ru_touchsearch_text_science
  Change       : 1.64% | 7977063.11111 -> 7834447.11111

Suspected Commit Range
  2 commits in range
  https://chromium.googlesource.com/chromium/src/+log/100c919f8fc51a06aee219a6898424f006cca92a..f5cb683f8e23e164b8ff7049d877fe266d4e8209


Revision             Result                  N
chromium@443250      7977063 +- 223042       9        good
chromium@443347      7922277 +- 412085       14       good
chromium@443395      7977476 +- 224008       9        good
chromium@443398      7987120 +- 229759       14       good
chromium@443399      8003128 +- 2489.38      6        good
chromium@443400      ---                     ---      build failure
chromium@443401      7929713 +- 295164       14       bad
chromium@443407      7962511 +- 2615.32      6        bad
chromium@443419      7849134 +- 275996       6        bad
chromium@443443      7834447 +- 330481       9        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/8989548017448143328

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


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

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