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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg0vrzrAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg0uv5rgoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgkuTxrAkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgkren8AsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgkv3o9AoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgkp-o-AgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgkpmeugsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg0v6I6ggM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgksH0sAsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgkrmuogsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgku_54QoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgks_TpAkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg0vygowkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgkt-kqwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgkvflrQsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgkoKrzgoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgkoKrzggM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg0sKUrAkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg0r7DogoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgksGqqQsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgkoOu7wgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgkoOurwsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg0r7ZvQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg0sLuogoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg0rCXqwkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgkvmhvwsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg0vjDpQsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgku_5oQkM


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

android-nexus5
android-nexus6
android-nexus7v2

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

=== BISECT JOB RESULTS ===
Bisect was unable to run to completion

Please try rerunning the bisect.


If failures persist contact the team (see below) and report the error.


Bisect Details
  Configuration: android_nexus7_perf_bisect
  Benchmark    : memory.top_10_mobile_stress
  Metric       : memory:chrome:all_processes:reported_by_chrome:skia:effective_size_avg/foreground/http_m_youtube_com_results_q_science

Revision             Result                   N
chromium@466807      4740187 +- 16289.2       14      good
chromium@467042      17607603 +- 2579501      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/8981247418704558176

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


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

=== BISECT JOB RESULTS ===
Bisect was unable to run to completion

Please try rerunning the bisect.


If failures persist contact the team (see below) and report the error.


Bisect Details
  Configuration: android_nexus7_perf_bisect
  Benchmark    : memory.top_10_mobile_stress
  Metric       : memory:chrome:all_processes:reported_by_chrome:skia:effective_size_avg/foreground/http_m_youtube_com_results_q_science
  Change       : 268.25% | 4721478.28571 -> 17306288.0

Revision             Result                  N
chromium@466807      4721478 +- 287669       14      good
chromium@467042      17306288 +- 255221      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/8981095013179365168

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


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

=== BISECT JOB RESULTS ===
Bisect was unable to run to completion

Please try rerunning the bisect.


If failures persist 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:gpu:effective_size_avg/background/after_http_m_youtube_com_results_q_science

Revision             Result              N
chromium@466800      1728576 +- 0.0      14      good
chromium@466998      5464128 +- 0.0      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/8980820958095627184

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


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