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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgwtCypQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgwuCeogsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgwrrQvgkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgwoyIvwsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDggp7s9AkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDggpapuQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDggv3DrwkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg_J_2uAoM


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

android-nexus5X
android-one

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

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

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

Revision             Result                    N
chromium@463663      19970124 +- 10164830      21      good
chromium@463683      20583632 +- 5604552       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 memory.top_10_mobile_stress

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

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


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

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

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

Revision             Result                   N
chromium@463663      20842989 +- 4080025      21      good
chromium@463683      21001267 +- 3705941      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 memory.top_10_mobile_stress

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

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


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

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

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

Revision             Result                   N
chromium@463663      16301434 +- 3628803      21      good
chromium@463683      16301657 +- 3629341      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 memory.top_10_mobile_stress

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

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


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

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

Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : memory.top_10_mobile_stress
  Metric       : memory:chrome:all_processes:reported_by_os:system_memory:native_heap:proportional_resident_size_avg/foreground/https_www_google_co_uk_hl_en_q_science

Revision             Result                   N
chromium@463663      65401000 +- 4578759      21      good
chromium@463683      65505205 +- 8941661      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 memory.top_10_mobile_stress

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

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


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