Reland "[heap] Optimize ArrayBuffer tracking"

Reland "[heap] Optimize ArrayBuffer tracking"

With the current approach we only need to track using an unordered set as we can
still access the backing store pointer and length by the time we free the
backing store.

Reland:
The issue was fixed in 67b5a501db179412479e827e51c43515e4196b27.

BUG=chromium:619491, chromium:611688
LOG=N
R=ulan@chromium.org

This reverts commit 0e1eaec71d5c6d05169308a71eaa51571e7c4f70.

Committed: https://crrev.com/f58dd088f0886f838f35a38613cd7b1a66f0cd63
Cr-Commit-Position: refs/heads/master@{#37399}

[Michael Lippautz, 2016-06-29 13:37:54]

Description was changed from

==========
Reland "[heap] Optimize ArrayBuffer tracking"

This reverts commit 0e1eaec71d5c6d05169308a71eaa51571e7c4f70.

BUG=
==========

to

==========
Reland "[heap] Optimize ArrayBuffer tracking"

With the current approach we only need to track using an unordered set as we can
still access the backing store pointer and length by the time we free the
backing store.

Reland:
The issue was fixed in 67b5a501db179412479e827e51c43515e4196b27.

BUG=chromium:619491, chromium:611688
LOG=N
R=ulan@chromium.org

This reverts commit 0e1eaec71d5c6d05169308a71eaa51571e7c4f70.
==========

[Michael Lippautz, 2016-06-29 13:37:55]

mlippautz@chromium.org changed reviewers:
+ ulan@chromium.org

[Michael Lippautz, 2016-06-29 13:37:55]

Description was changed from

==========
Reland "[heap] Optimize ArrayBuffer tracking"

This reverts commit 0e1eaec71d5c6d05169308a71eaa51571e7c4f70.

BUG=
==========

to

==========
Reland "[heap] Optimize ArrayBuffer tracking"

With the current approach we only need to track using an unordered set as we can
still access the backing store pointer and length by the time we free the
backing store.

Reland:
The issue was fixed in 67b5a501db179412479e827e51c43515e4196b27.

BUG=chromium:619491, chromium:611688
LOG=N
R=ulan@chromium.org

This reverts commit 0e1eaec71d5c6d05169308a71eaa51571e7c4f70.
==========

[Michael Lippautz, 2016-06-29 13:37:55]

mlippautz@chromium.org changed reviewers:
+ ulan@chromium.org

[Michael Lippautz, 2016-06-29 13:38:47]

The CQ bit was checked by mlippautz@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2016-06-29 13:38:57]

Dry run: CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[ulan, 2016-06-29 13:46:29]

lgtm

[commit-bot: I haz the power, 2016-06-29 14:04:22]

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

[commit-bot: I haz the power, 2016-06-29 14:04:23]

Dry run: This issue passed the CQ dry run.

[Michael Lippautz, 2016-06-29 14:51:25]

The CQ bit was checked by mlippautz@chromium.org

[commit-bot: I haz the power, 2016-06-29 14:51:35]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-06-29 14:53:47]

Description was changed from

==========
Reland "[heap] Optimize ArrayBuffer tracking"

With the current approach we only need to track using an unordered set as we can
still access the backing store pointer and length by the time we free the
backing store.

Reland:
The issue was fixed in 67b5a501db179412479e827e51c43515e4196b27.

BUG=chromium:619491, chromium:611688
LOG=N
R=ulan@chromium.org

This reverts commit 0e1eaec71d5c6d05169308a71eaa51571e7c4f70.
==========

to

==========
Reland "[heap] Optimize ArrayBuffer tracking"

With the current approach we only need to track using an unordered set as we can
still access the backing store pointer and length by the time we free the
backing store.

Reland:
The issue was fixed in 67b5a501db179412479e827e51c43515e4196b27.

BUG=chromium:619491, chromium:611688
LOG=N
R=ulan@chromium.org

This reverts commit 0e1eaec71d5c6d05169308a71eaa51571e7c4f70.
==========

[commit-bot: I haz the power, 2016-06-29 14:53:48]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-06-29 14:54:39]

Description was changed from

==========
Reland "[heap] Optimize ArrayBuffer tracking"

With the current approach we only need to track using an unordered set as we can
still access the backing store pointer and length by the time we free the
backing store.

Reland:
The issue was fixed in 67b5a501db179412479e827e51c43515e4196b27.

BUG=chromium:619491, chromium:611688
LOG=N
R=ulan@chromium.org

This reverts commit 0e1eaec71d5c6d05169308a71eaa51571e7c4f70.
==========

to

==========
Reland "[heap] Optimize ArrayBuffer tracking"

With the current approach we only need to track using an unordered set as we can
still access the backing store pointer and length by the time we free the
backing store.

Reland:
The issue was fixed in 67b5a501db179412479e827e51c43515e4196b27.

BUG=chromium:619491, chromium:611688
LOG=N
R=ulan@chromium.org

This reverts commit 0e1eaec71d5c6d05169308a71eaa51571e7c4f70.

Committed: https://crrev.com/f58dd088f0886f838f35a38613cd7b1a66f0cd63
Cr-Commit-Position: refs/heads/master@{#37399}
==========

[commit-bot: I haz the power, 2016-06-29 14:54:40]

Patchset 1 (id:??) landed as
https://crrev.com/f58dd088f0886f838f35a38613cd7b1a66f0cd63
Cr-Commit-Position: refs/heads/master@{#37399}