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

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


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

android-nexus7v2

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

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

Hi ishell@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 : 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_nexus7_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:v8:effective_size_avg/load_games/load_games_lazors
  Change       : 0.52% | 2451698.66667 -> 2464484.66667

Revision                           Result                  N
chromium@442712                    2451699 +- 184.405      6      good
chromium@442747                    2452038 +- 186.226      6      good
chromium@442765                    2452029 +- 201.17       6      good
chromium@442770                    2452063 +- 254.585      6      good
chromium@442770,v8@8e9c90baa0      2451995 +- 47.4693      6      good
chromium@442770,v8@de24227234      2464437 +- 226.392      6      bad       <--
chromium@442770,v8@6921b71d41      2464605 +- 667.471      6      bad
chromium@442771                    2464479 +- 286.366      6      bad
chromium@442772                    2464437 +- 226.392      6      bad
chromium@442774                    2464441 +- 225.737      6      bad
chromium@442782                    2464485 +- 277.729      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.games.lazors system_health.memory_mobile

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

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


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

This bug has an owner, but was in a state that our triage picked up. Marking as Assigned.

This is a 12kib regression. We've fixed our monitoring to ignore regressions < 128kib. WontFix-ing.