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

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


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

android-nexus6

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

=== 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 : 08879a1263f332c02ff6ad2d6179fc8a20af4901
  Date   : Fri Apr 28 05:21:32 2017
  Subject: Remove resize fade delay plumbing.

Bisect Details
  Configuration: android_nexus6_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_os:system_memory:java_heap:proportional_resident_size_avg/load_tools/load_tools_dropbox
  Change       : 30.92% | 14769493.3333 -> 19335606.8571

Revision             Result                    N
chromium@467799      14769493 +- 315317        21      good
chromium@467858      14762569 +- 179043        14      good
chromium@467887      14775223 +- 264963        14      good
chromium@467891      14795995 +- 318943        14      good
chromium@467893      14776434 +- 191312        9       good
chromium@467894      14765284 +- 215156        9       good
chromium@467895      14889033 +- 271321        14      bad       <--
chromium@467902      14880110 +- 330635        14      bad
chromium@467916      14899127 +- 300269        14      bad
chromium@468032      19335607 +- 10803442      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.tools.dropbox system_health.memory_mobile

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

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


| 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 recovered sometime around r469319.

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