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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgksDbqQsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgkrrCtAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgkuDcugoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg4ueLrQkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgksr1_AgM


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

android-nexus5X
android-one

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

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

Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : memory.top_10_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:gpu:effective_size_avg/foreground/https_mobile_twitter_com_justinbieber_skip_interstitial_true

Revision             Result                   N
chromium@466675      1246264 +- 0.0           21      good
chromium@466754      4588600 +- 31575790      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 memory.top_10_mobile

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

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


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

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

Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : memory.top_10_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:gpu:effective_size_avg/foreground/https_mobile_twitter_com_justinbieber_skip_interstitial_true

Revision             Result                   N
chromium@466675      1246264 +- 0.0           21      good
chromium@466754      4588600 +- 31575790      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 memory.top_10_mobile

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

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


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

=== BISECT JOB RESULTS ===
Perf regression found with culprit

Suspected Commit
  Author : skobes
  Commit : 8a4d4531daca4b9a1f6dc1224bcb7134dc053ff4
  Date   : Mon Apr 24 19:19:10 2017
  Subject: Temporarily ignore ScrollbarAnimationController::DidRequestShowFromMainThread.

Bisect Details
  Configuration: android_one_perf_bisect
  Benchmark    : memory.top_10_mobile
  Metric       : memory:chrome:all_processes:reported_by_os:system_memory:private_dirty_size_avg/background/after_http_www_baidu_com_s_word_google
  Change       : 4.28% | 27959615.3333 -> 29157012.6667

Revision             Result                   N
chromium@466676      27959615 +- 818097       6       good
chromium@466698      28014229 +- 1066978      9       good
chromium@466709      28091857 +- 2241683      14      good
chromium@466711      27354087 +- 941610       6       good
chromium@466712      28848153 +- 2180004      14      bad       <--
chromium@466715      29215267 +- 800290       9       bad
chromium@466720      29228921 +- 975200       9       bad
chromium@466763      29157013 +- 621345       6       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 memory.top_10_mobile

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

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


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