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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgxOfpigsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgpNnunAsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgpOqE9QgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgpOr2_QsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgpIGzuAkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg5IDd7QoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgpI6t7wgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgpNfE6gsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgpKvZtQsM


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

android-nexus5X

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

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

Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : memory.top_10_mobile
  Metric       : memory:chrome:all_processes:reported_by_os:system_memory:java_heap:proportional_resident_size_avg/foreground/https_mobile_twitter_com_justinbieber_skip_interstitial_true

Revision             Result                 N
chromium@453569      8321024 +- 816716      21      good
chromium@453596      8295424 +- 826725      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

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

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


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

ref build moves too.