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

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


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

android-nexus5
android-one

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

=== 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_chrome:v8:effective_size_avg/background/after_https_mobile_twitter_com_justinbieber_skip_interstitial_true

Revision             Result                  N
chromium@459644      2465146 +- 44274.3      21      good
chromium@459648      2459138 +- 46429.7      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/8983993839637437008

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


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