Closed
Bug 758398
Opened 12 years ago
Closed 12 years ago
"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)
Categories
(Core :: JavaScript Engine, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 757682
People
(Reporter: gkw, Unassigned)
References
Details
(Keywords: assertion, regression, testcase, Whiteboard: js-triage-needed)
Attachments
(1 file)
|
(deleted),
text/plain
|
Details |
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
|
||
Updated•12 years ago
|
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → DUPLICATE
|
||
Updated•11 years ago
|
Group: core-security
You need to log in
before you can comment on or make changes to this bug.
Description
•