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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDglMHOjQgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg1I6KoQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg1IDUoAkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg1MGe5goM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDglMGD_QoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDglIeDugkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg1IODsgoM


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

android-nexus5
android-nexus5X
android-nexus6
android-nexus7v2

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

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

Suspected Commit
  Author : pdr
  Commit : a20ad732333dc9db2b545886acd16a11abdc5842
  Date   : Tue Mar 07 17:11:15 2017
  Subject: Remove indirection: setup scrollbar scroll layers in the scrollbar constructor

Bisect Details
  Configuration: android_nexus7_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:gpu:effective_size_avg/load_social/load_social_twitter
  Change       : 1024.11% | 1246264.0 -> 14009400.0

Revision             Result                    N
chromium@455082      1246264 +- 0.0            6      good
chromium@455100      1246264 +- 0.0            6      good
chromium@455103      1246264 +- 0.0            6      good
chromium@455104      1246264 +- 0.0            6      good
chromium@455105      14009400 +- 0.0           6      bad       <--
chromium@455109      14009400 +- 0.0           6      bad
chromium@455117      11882211 +- 11651096      6      bad
chromium@455151      11882211 +- 11651096      6      bad
chromium@455220      14009400 +- 0.0           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 --story-filter=load.social.twitter system_health.memory_mobile

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

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


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