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

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


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

android-nexus5
android-nexus7v2

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

=== BISECT JOB RESULTS ===
Perf regression found but unable to continue

Bisect was stopped because a commit couldn't be classified as either
good or bad.


Bisect Details
  Configuration: android_nexus7_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@441469      21467093 +- 675009      21      good
chromium@441497      21560945 +- 574048      21      unknown
chromium@441525      21597234 +- 672115      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/8990897279816988400

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


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

regression too small, might just be noise.