Remove m_domDataStoreList from V8PerIsolateData

Remove m_domDataStoreList from V8PerIsolateData

- This CL removes V8PerIsolateData::m_domDataStoreList and related methods.

- The only customer of these methods is SerializedScriptValue::neuterBinding(). This CL replaces it to use DOMWrapperWorld::allWorldsInMainThread() instead.

BUG=341032
NOTRY=true

Committed: https://src.chromium.org/viewvc/blink?view=rev&revision=168347

[haraken, 2014-02-27 05:00:51]

PTAL

https://codereview.chromium.org/182513003/diff/2/Source/bindings/v8/Serialize...
File Source/bindings/v8/SerializedScriptValue.cpp (left):

https://codereview.chromium.org/182513003/diff/2/Source/bindings/v8/Serialize...
Source/bindings/v8/SerializedScriptValue.cpp:2339: v8::Handle<v8::Object>
wrapper = allStores[i]->get<V8ArrayBuffer>(object, isolate);

This CL keeps the current behavior, but I don't fully understand what
neuterBinding() is doing. Why do we need to neuter ArrayBuffer wrappers in
different worlds in the main thread?

[dcarney, 2014-02-27 07:20:50]

lgtm

https://codereview.chromium.org/182513003/diff/2/Source/bindings/v8/Serialize...
File Source/bindings/v8/SerializedScriptValue.cpp (left):

https://codereview.chromium.org/182513003/diff/2/Source/bindings/v8/Serialize...
Source/bindings/v8/SerializedScriptValue.cpp:2339: v8::Handle<v8::Object>
wrapper = allStores[i]->get<V8ArrayBuffer>(object, isolate);
On 2014/02/27 05:00:51, haraken wrote:
> 
> This CL keeps the current behavior, but I don't fully understand what
> neuterBinding() is doing. Why do we need to neuter ArrayBuffer wrappers in
> different worlds in the main thread?

the arraybuffer might only exist in one world, but you can't know in advance
where it lives.

[Dmitry Lomov (no reviews), 2014-02-27 09:09:13]

lgtm

[haraken, 2014-02-27 10:55:27]

The CQ bit was checked by haraken@chromium.org

[commit-bot: I haz the power, 2014-02-27 10:55:35]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/haraken@chromium.org/182513003/30001

[commit-bot: I haz the power, 2014-02-27 11:52:22]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2014-02-27 11:52:23]

Retried try job too often on mac_blink_rel for step(s) blink_heap_unittests,
blink_platform_unittests, webkit_lint, webkit_python_tests, webkit_tests,
webkit_unit_tests, wtf_unittests
http://build.chromium.org/p/tryserver.chromium/buildstatus?builder=mac_blink_...

[haraken, 2014-03-03 13:10:51]

The CQ bit was checked by haraken@chromium.org

[commit-bot: I haz the power, 2014-03-03 13:11:22]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/haraken@chromium.org/182513003/50001

[commit-bot: I haz the power, 2014-03-03 16:52:48]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2014-03-03 16:52:49]

Retried try job too often on win_layout for step(s) webkit_lint
http://build.chromium.org/p/tryserver.chromium/buildstatus?builder=win_layout...

[haraken, 2014-03-03 23:17:38]

The CQ bit was checked by haraken@chromium.org

[commit-bot: I haz the power, 2014-03-03 23:18:42]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/haraken@chromium.org/182513003/50001

[commit-bot: I haz the power, 2014-03-03 23:18:47]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2014-03-03 23:18:47]

Failed to apply the patch.
<?xml version="1.0"?>
<status>
<target
   path=".">

[haraken, 2014-03-04 00:49:08]

The CQ bit was checked by haraken@chromium.org

[commit-bot: I haz the power, 2014-03-04 00:49:17]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/haraken@chromium.org/182513003/70001

[commit-bot: I haz the power, 2014-03-04 00:49:30]

Change committed as 168347