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

=== 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 : bcb3af59be2c52ca13a0adae500f042a64093b6d
  Date   : Sun Nov 13 09:38:15 2016
  Subject: [ic] Support data handlers that represent transitioning stores.

Bisect Details
  Configuration: android_nexus9_perf_bisect
  Benchmark    : memory.top_10_mobile
  Metric       : memory:chrome:renderer_processes:reported_by_chrome:v8:heap:large_object_space:effective_size_avg/background/after_http_www_baidu_com_s_word_google

Revision                           Result             N
chromium@431807                    0.0 +- 0.0         6      good
chromium@431856                    0.0 +- 0.0         6      good
chromium@431862                    0.0 +- 0.0         6      good
chromium@431864                    0.0 +- 0.0         6      good
chromium@431864,v8@5d3ce7ea4f      0.0 +- 0.0         6      good
chromium@431864,v8@bcb3af59be      524288 +- 0.0      6      bad       <--
chromium@431864,v8@a9f553bada      524288 +- 0.0      6      bad
chromium@431865                    524288 +- 0.0      6      bad
chromium@431868                    524288 +- 0.0      6      bad
chromium@431880                    524288 +- 0.0      6      bad
chromium@431904                    524288 +- 0.0      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=http.www.baidu.com.s.word.google memory.top_10_mobile

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

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


| 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 went definitely wrong here:
1) My CL does nothing with large space.
2) I don't beleve zero result for chromium@431864,v8@5d3ce7ea4f

Restarted the bisection.

The regression is only indirectly caused by this CL (code-space size increases push some snapshot allocations to LO space). See https://bugs.chromium.org/p/v8/issues/detail?id=5831.

Can't merge into a V8 issue, so closing as WontFix.