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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDggPXkqgoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDggMnJsAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDggKydrwsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg_7_-tQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg_73k8AgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDggMzatAoM


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

android-nexus7v2
android-one

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

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

Bisect Details
  Configuration: android_one_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:malloc:effective_size_avg/load_tools/load_tools_drive

Revision             Result                  N
chromium@441306      17069517 +- 825443      21      good
chromium@441327      17207446 +- 686871      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=load.tools.drive system_health.memory_mobile

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

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


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

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

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

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

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

Bisect Details
  Configuration: android_nexus7_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:malloc:effective_size_avg/load_social/load_social_facebook

Revision             Result                  N
chromium@441274      21675727 +- 523496      21      good
chromium@441407      21741016 +- 591735      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=load.social.facebook system_health.memory_mobile

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

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


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

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

Bisect Details
  Configuration: android_one_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:malloc:effective_size_avg/load_tools/load_tools_drive

Revision             Result                  N
chromium@441306      17120673 +- 701860      21      good
chromium@441343      17026542 +- 906523      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=load.tools.drive system_health.memory_mobile

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

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


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

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

Bisect Details
  Configuration: android_one_perf_bisect
  Benchmark    : memory.top_10_mobile_stress
  Metric       : memory:chrome:all_processes:reported_by_chrome:malloc:effective_size_avg/foreground/http_yandex_ru_touchsearch_text_science

Revision             Result                  N
chromium@441265      14104895 +- 496140      21      good
chromium@441327      14134653 +- 567316      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=http.yandex.ru.touchsearch.text.science memory.top_10_mobile_stress

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

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


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

Again - small - not reproducible. It's likely noise || Swarming.