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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg-pPvgwgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDghqLk4wkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDghoHstgsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDghpqG-goM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg-q-TrQsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDghtnPvAkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg-t2-7QoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDghqLk4woM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg-q-TrQkM


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

android-nexus5X
android-nexus7v2

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

=== 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:private_dirty_size_avg/foreground/http_en_m_wikipedia_org_wiki_Science

Revision             Result                    N
chromium@475226      82479910 +- 9798947       21      good
chromium@475243      82669496 +- 11515253      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/8978200461640689568

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


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

=== 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:private_dirty_size_avg/foreground/http_en_m_wikipedia_org_wiki_Science

Revision             Result                    N
chromium@475226      82089424 +- 10620225      21      good
chromium@475243      81930266 +- 8288085       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/8978182102468351888

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


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