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

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


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

android-nexus5

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

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

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

Hi mvstanton@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 : mvstanton
  Commit : 38602f1ff553b32815d34a05cd6d965f4fc20960
  Date   : Mon Jan 09 15:31:00 2017
  Subject: [FeedbackVector] Infrastructure for literal arrays in the vector.

Bisect Details
  Configuration: android_nexus5_perf_bisect
  Benchmark    : v8.browsing_mobile
  Metric       : v8-gc-full-mark-compactor_sum/browse_news/browse_news_qq
  Change       : 135.67% | 58.24425 -> 137.266

Revision                           Result                  N
chromium@442254                    58.2443 +- 15.8146      8       good
chromium@442298                    64.1629 +- 25.9863      7       good
chromium@442309                    62.2631 +- 28.3853      12      good
chromium@442312                    64.7434 +- 82.1856      10      good
chromium@442312,v8@e7fc42796c      57.2265 +- 8.87636      6       good
chromium@442312,v8@38602f1ff5      125.971 +- 68.298       6       bad       <--
chromium@442313                    132.468 +- 13.1156      6       bad
chromium@442314                    137.125 +- 12.8552      6       bad
chromium@442315                    128.32 +- 57.9391       11      bad
chromium@442320                    133.605 +- 11.9275      7       bad
chromium@442341                    137.266 +- 18.3509      5       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.qq v8.browsing_mobile

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

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


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

=== 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_nexus5_perf_bisect
  Benchmark    : v8.browsing_mobile
  Metric       : v8-gc-full-mark-compactor_sum/browse_news/browse_news_qq
  Change       : 145.47% | 55.5648333333 -> 136.3974

Suspected Commit Range
  2 commits in range
  https://chromium.googlesource.com/v8/v8.git/+log/e7fc42796c823fdee6b4f812f798679df42fba0c..db76e7af00fca3256a97937ba8fbdecf6dd76cd4


Revision                           Result                  N
chromium@442203                    55.5648 +- 6.90934      6        good
chromium@442297                    59.7513 +- 18.7173      6        good
chromium@442309                    64.5264 +- 65.0993      11       good
chromium@442312                    75.0866 +- 108.821      10       good
chromium@442312,v8@e7fc42796c      65.9782 +- 71.0052      8        good
chromium@442312,v8@38602f1ff5      ---                     ---      build failure
chromium@442312,v8@db76e7af00      136.135 +- 16.6593      5        bad
chromium@442313                    136.389 +- 17.2699      16       bad
chromium@442314                    137.962 +- 26.4089      15       bad
chromium@442315                    138.89 +- 22.298        8        bad
chromium@442321                    132.57 +- 8.32387       6        bad
chromium@442344                    133.049 +- 16.1727      7        bad
chromium@442391                    136.397 +- 7.57853      5        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.qq v8.browsing_mobile

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

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


| 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 was part of an attempt to change rooting of the feedback vector. After a couple of reverts we succeeded. Marking this wontfix.