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

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


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

android-nexus6

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

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

Suspected Commit
  Author : ishell
  Commit : de2422723435b0a35bbea93fa42fb07ddfed0109
  Date   : Tue Jan 10 15:45:11 2017
  Subject: [ic][stubs] Move more IC-related methods from CSA to AccessorAssembler.

Bisect Details
  Configuration: android_nexus6_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:v8:effective_size_avg/blank_about/blank_about_blank
  Change       : 0.68% | 1874084.0 -> 1886805.33333

Revision                           Result                  N
chromium@442703                    1874084 +- 274.343      6      good
chromium@442738                    1874425 +- 258.653      6      good
chromium@442756                    1874500 +- 0.0          6      good
chromium@442765                    1874485 +- 257.273      6      good
chromium@442769                    1874522 +- 120.499      6      good
chromium@442770                    1874463 +- 204.483      6      good
chromium@442770,v8@8e9c90baa0      1874463 +- 204.483      6      good
chromium@442770,v8@de24227234      1886903 +- 127.802      6      bad       <--
chromium@442770,v8@6921b71d41      1886805 +- 258.653      6      bad
chromium@442771                    1886805 +- 258.653      6      bad
chromium@442773                    1886805 +- 258.653      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=blank.about.blank system_health.memory_mobile

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

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


| 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 Tests>AutoBisect.  Thank you!