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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDggImBqgoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDggKeUugoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDggNyeoQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg_7-vogkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDggJiNqAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg_7OotQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDggOXPtAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDggLHLvgoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg_9PjuQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg__X2tQkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg_6fStAkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg_-eVrwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg_52enAgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDggObOoAsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDggOHArAoM


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

android-nexus5
android-nexus7v2

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

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

Bisect Details
  Configuration: android_nexus5_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_os:system_memory:native_heap:proportional_resident_size_avg/load_search/load_search_google

Revision             Result                   N
chromium@441403      23319213 +- 2193461      21      good
chromium@441406      23584283 +- 2491831      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.search.google system_health.memory_mobile

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

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


| 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/8990895567267024624

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

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

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

Bisect Details
  Configuration: android_nexus5_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:malloc:effective_size_avg/load_media/load_media_facebook_photos

Revision             Result                  N
chromium@441403      21617147 +- 428595      21      good
chromium@441417      21666334 +- 577116      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.media.facebook.photos system_health.memory_mobile

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

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


| 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_nexus5_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:malloc:effective_size_avg/load_news/load_news_sohu

Revision             Result                  N
chromium@441403      19875149 +- 500426      21      good
chromium@441417      19858315 +- 629600      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.news.sohu system_health.memory_mobile

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

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


| 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_nexus5_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_os:system_memory:native_heap:proportional_resident_size_avg/load_search/load_search_google

Revision             Result                   N
chromium@441403      23352957 +- 2550659      21      good
chromium@441417      23673712 +- 2394831      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.search.google system_health.memory_mobile

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

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


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

I don't know what's going on with this metric this week, but I'm guessing this is also machine related, or possibly swarming related. It's small and not reproducible by bisect bots. WontFix.

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

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

Bisect Details
  Configuration: android_nexus5_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_os:system_memory:native_heap:proportional_resident_size_avg/load_search/load_search_google

Revision             Result                   N
chromium@441403      23346032 +- 2278261      21      good
chromium@441417      23387382 +- 2409294      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 --story-filter=load.search.google system_health.memory_mobile

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

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


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