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

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


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

android-one

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

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

Bisect Details
  Configuration: android_one_perf_bisect
  Benchmark    : memory.top_10_mobile
  Metric       : memory:chrome:all_processes:reported_by_os:system_memory:private_dirty_size_avg/foreground/http_www_amazon_com_gp_aw_s_k_nexus

Revision             Result                   N
chromium@448038      38982590 +- 2337895      21      good
chromium@448079      39187780 +- 2392159      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/8988025163064795056

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


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

I think this is just a duplicate of 689834.

https://screenshot.googleplex.com/B6tqaCBQ8w1