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

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


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

android-nexus7v2

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

=== BISECT JOB RESULTS ===
Perf regression found but unable to narrow commit range

Build failures prevented the bisect from narrowing the range further.


Bisect Details
  Configuration: android_nexus7_perf_bisect
  Benchmark    : v8.browsing_mobile_ignition
  Metric       : memory:chrome:renderer_processes:reported_by_chrome:v8:code_and_metadata_size_max/browse_news/browse_news_washingtonpost
  Change       : 1.05% | 2464145.33333 -> 2489932.66667

Suspected Commit Range
  15 commits in range
  https://chromium.googlesource.com/chromium/src/+log/9422f34b57066a40cea5b40c1e022adeb4712859..d6539dc7b85800f035f1a14e06653497a45aab0c


Revision             Result                  N
chromium@442711      2464145 +- 34700.2      9        good
chromium@442729      2459416 +- 46088.2      14       good
chromium@442730      ---                     ---      build failure
---                  ---                     ---      too many build failures to list
chromium@442743      ---                     ---      build failure
chromium@442744      2476817 +- 66868.0      21       bad
chromium@442747      2474509 +- 61980.9      14       bad
chromium@442782      2489933 +- 4559.83      6        bad

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 v8.browsing_mobile_ignition

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

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


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

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

Monorail isn't updating this bug, I filed https://bugs.chromium.org/p/monorail/issues/detail?id=2214 for the problem.

The bisect thinks this is https://codereview.chromium.org/2619823005, assigning to ishell

=== 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    : v8.browsing_mobile_ignition
  Metric       : memory:chrome:renderer_processes:reported_by_chrome:code_and_metadata_size_max/browse_news/browse_news_washingtonpost
  Change       : 0.88% | 2474430.22222 -> 2496312.0

Revision                           Result                  N
chromium@442711                    2474430 +- 46528.4      9      good
chromium@442747                    2469076 +- 20869.3      6      good
chromium@442765                    2466956 +- 25804.0      6      good
chromium@442770                    2465810 +- 34598.5      9      good
chromium@442770,v8@8e9c90baa0      2462210 +- 17511.1      6      good
chromium@442770,v8@de24227234      2494658 +- 39240.8      9      bad       <--
chromium@442770,v8@6921b71d41      2495578 +- 20626.0      6      bad
chromium@442771                    2493608 +- 21703.0      6      bad
chromium@442772                    2498395 +- 37457.1      6      bad
chromium@442774                    2493167 +- 50944.7      9      bad
chromium@442782                    2496312 +- 30191.6      9      bad

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 v8.browsing_mobile_ignition

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

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


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