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

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


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

android-nexus5

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

=== 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:v8:effective_size_avg/load_search/load_search_ebay

Revision             Result                 N
chromium@467801      3688113 +- 278818      21      good
chromium@468086      3857807 +- 712414      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.ebay system_health.memory_mobile

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

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


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

=== Auto-CCing suspected CL author skobes@chromium.org ===

Hi skobes@chromium.org, the bisect results pointed to your CL, please take a look at the
results.


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

Suspected Commit
  Author : skobes
  Commit : 697a467f819ce09da5209a3df13b8b92f33e35a4
  Date   : Fri Apr 28 02:54:17 2017
  Subject: Call SAC::DidScrollUpdate only for compositor-triggered scrolls.

Bisect Details
  Configuration: android_nexus5_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:v8:effective_size_avg/load_search/load_search_ebay
  Change       : 7.04% | 3677460.66667 -> 3936215.33333

Revision             Result                  N
chromium@467801      3677461 +- 59186.4      6       good
chromium@467837      3693668 +- 50397.4      9       good
chromium@467846      3692997 +- 53880.4      9       good
chromium@467851      3695490 +- 73053.6      9       good
chromium@467853      3686892 +- 62271.3      9       good
chromium@467854      3687330 +- 36125.9      9       good
chromium@467855      3784969 +- 483399       14      bad       <--
chromium@467873      3841550 +- 400315       9       bad
chromium@467944      3905305 +- 286836       6       bad
chromium@468086      3936215 +- 238772       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.search.ebay system_health.memory_mobile

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

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


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

This graph looks like it went back down around r469654.

https://chromeperf.appspot.com/group_report?bug_id=717153