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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg0pfUrAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg0rWJpAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg0v_XuAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg0pX4pQoM


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

android-nexus6

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

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

Hi littledan@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 : Daniel Ehrenberg
  Commit : 4968b2c4d1692cc18f2d8cca5b9b24bd038ea8f1
  Date   : Mon Apr 24 14:03:38 2017
  Subject: [intl] Switch to using declared accessors

Bisect Details
  Configuration: android_nexus6_perf_bisect
  Benchmark    : v8.runtimestats.browsing_mobile
  Metric       : v8-gc-latency-mark-compactor_max/browse_shopping/browse_shopping_avito
  Change       : 433.05% | 19.7391666667 -> 105.2205

Revision                           Result                  N
chromium@467310                    19.7392 +- 6.31836      6      good
chromium@467317                    18.552 +- 5.7529        6      good
chromium@467320                    21.2168 +- 5.88869      6      good
chromium@467321                    20.1533 +- 8.77551      6      good
chromium@467321,v8@f06db79c67      20.3517 +- 4.45486      6      good
chromium@467321,v8@54190d304e      18.1882 +- 4.74062      6      good
chromium@467321,v8@4968b2c4d1      104.614 +- 7.31439      6      bad       <--
chromium@467321,v8@7f7d445ff6      106.217 +- 12.4005      6      bad
chromium@467321,v8@d853b2382e      96.0097 +- 26.0566      6      bad
chromium@467321,v8@a1af3315a2      102.701 +- 12.3413      6      bad
chromium@467322                    106.233 +- 22.1014      6      bad
chromium@467323                    97.7727 +- 16.5847      6      bad
chromium@467335                    107.074 +- 17.0508      6      bad
chromium@467360                    105.091 +- 14.3686      6      bad
chromium@467410                    105.221 +- 4.44322      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.shopping.avito v8.runtimestats.browsing_mobile

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

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


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

Well, a new revision of V8 recovered on this benchmark, where the only CLs were reverting this patch and a DEPS upgrade. So I'll keep it reverted and look further into what's going on here. Thanks for the sheriffing, Jakob.