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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg9LDu_AkM


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

android-nexus5X

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

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

=== BISECT JOB RESULTS ===
Bisect failed for unknown reasons

Please contact the team (see below) and report the error.


Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_os:gpu_memory:proportional_resident_size_avg/browse_news/browse_news_washingtonpost


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.news.washingtonpost system_health.memory_mobile

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

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


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

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

Suspected Commit
  Author : pdr
  Commit : 53707d796144fb0c60f081e4477b31a7adab4e6d
  Date   : Thu Mar 09 19:30:09 2017
  Subject: Revert of Remove indirection: setup scrollbar scroll layers in the scrollbar constructor (patchset #5 id:80001 of https://codereview.chromium.org/2728253002/ )

Bisect Details
  Configuration: android_nexus7_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_os:gpu_memory:proportional_resident_size_avg/load_media/load_media_flickr
  Change       : 28.79% | 63778816.0 -> 82139818.6667

Revision             Result                    N
chromium@455773      63778816 +- 0.0           6      good
chromium@455826      63781547 +- 14956.5       6      good
chromium@455827      63781547 +- 14956.5       6      good
chromium@455828      82134357 +- 18918.6       6      bad       <--
chromium@455830      82131627 +- 14956.5       6      bad
chromium@455833      82134357 +- 18918.6       6      bad
chromium@455840      79089664 +- 16754332      6      bad
chromium@455853      82131627 +- 14956.5       6      bad
chromium@455879      82139819 +- 59825.9       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.media.flickr system_health.memory_mobile

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

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


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