758398 - "Assertion failure: key == JSProto_Int8Array || key == JSProto_Uint8Array || key == JSProto_Int16Array || key == JSProto_Uint16Array || key == JSProto_Int32Array || key == JSProto_Uint32Array || .." (truncated because assertion message is too long)

Status: RESOLVED DUPLICATE of bug 757682

(Core :: JavaScript Engine, defect)

Description

[Gary Kwong [:gkw] [:nth10sd] (NOT official MoCo now)]

Attachment: stack

x = [];
x.unshift(ArrayBuffer());
x.map(DataView);

asserts js debug shell on m-c changeset c20d415ef1b5 with -n at Assertion failure: key == JSProto_Int8Array || key == JSProto_Uint8Array || key == JSProto_Int16Array || key == JSProto_Uint16Array || key == JSProto_Int32Array || key == JSProto_Uint32Array || key == JSProto_Float32Array || key == JSProto_Float64Array || key == JSProto_Uint8ClampedArray,

ArrayBuffer bugs have been known to be s-s in the past, so setting this one s-s as well unless otherwise shown.

autoBisect shows this is probably related to the following changeset:

The first bad revision is:
changeset:   94163:73b380d3edd8
user:        Steve Fink
date:        Wed Mar 28 14:43:02 2012 -0700
summary:     Bug 741041 - Use UnwrapObjectChecked, and ensure ArrayBufferViews and their buffers are in the same compartment. r=luke