Set ArrayBufferContents size to 0 on allocation failure

Set ArrayBufferContents size to 0 on allocation failure

Also, add a RELEASE_ASSERT when creating an ArrayBuffer from an
ArrayBufferContents that the backing store is non-NULL.

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

[adamk, 2015-08-20 23:15:11]

adamk@chromium.org changed reviewers:
+ adamk@chromium.org

[adamk, 2015-08-20 23:15:12]

I'm not a wtf owner, so I won't be able to help much, but it looks like you have
two mitigations in here (the other being crashing if an ArrayBuffer is
constructed with an ArrayBufferContents whose data is null).

[binji, 2015-08-20 23:17:10]

On 2015/08/20 at 23:15:12, adamk wrote:
> I'm not a wtf owner, so I won't be able to help much, but it looks like you
have two mitigations in here (the other being crashing if an ArrayBuffer is
constructed with an ArrayBufferContents whose data is null).

Yes, I suppose I should call it out in the CL description.

[binji, 2015-08-20 23:23:40]

binji@chromium.org changed reviewers:
+ cevans@chromium.org

[binji, 2015-08-20 23:24:54]

binji@chromium.org changed reviewers:
+ jchaffraix@chromium.org
- cevans@chromium.org

[binji, 2015-08-20 23:24:55]

+jchaffraix for OWNERS

[adamk, 2015-08-20 23:36:23]

adamk@chromium.org changed reviewers:
+ haraken@chromium.org, tkent@chromium.org

[adamk, 2015-08-20 23:36:24]

+ a few more wtf OWNERs just in case

[tkent, 2015-08-21 00:05:20]

lgtm

[haraken, 2015-08-21 00:09:08]

LGTM

[binji, 2015-08-21 01:33:37]

The CQ bit was checked by binji@chromium.org

[commit-bot: I haz the power, 2015-08-21 01:34:02]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1302193002/1
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1302193002/1

[commit-bot: I haz the power, 2015-08-21 04:40:46]

Committed patchset #1 (id:1) as
https://src.chromium.org/viewvc/blink?view=rev&revision=200961