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

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


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

android-one

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

=== 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:malloc:effective_size_avg/foreground/https_www_google_co_uk_hl_en_q_science

Revision             Result                  N
chromium@441306      13775683 +- 429345      21      good
chromium@441329      13808304 +- 401579      21      bad

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 --story-filter=https.www.google.co.uk.hl.en.q.science memory.top_10_mobile

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

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


| 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 Tests>AutoBisect.  Thank you!

Blocked on being able to reliably repro memory regressions on bisect bots.

bisect bot could not repro.