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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgzoHmpwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgjo7O8QgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgjqaMowoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgjuiE4woM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgjuSI5ggM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgjo-RtQkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgjo-RtQoM


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

android-nexus5X
android-webview-nexus5X

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

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

Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:cc:effective_size_avg/browse_social/browse_social_instagram

Revision             Result                      N
chromium@480379      175399004 +- 64555977       21      good
chromium@480528      181463992 +- 142218118      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=browse.social.instagram system_health.memory_mobile

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

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


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

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

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

Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:cc:effective_size_avg/browse_social/browse_social_instagram

Revision             Result                      N
chromium@480379      177651250 +- 70709662       21      good
chromium@480528      186088695 +- 136807700      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=browse.social.instagram system_health.memory_mobile

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

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


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