Closed Bug 722021 Opened 13 years ago Closed 13 years ago

Assertion failure: key.index() >= 0, at methodjit/BaseAssembler.h:788

Categories

(Core :: JavaScript Engine, defect)

x86_64
Linux
defect
Not set
critical

Tracking

()

RESOLVED FIXED
mozilla13

People

(Reporter: decoder, Assigned: bhackett1024)

Details

(Keywords: assertion, testcase, Whiteboard: js-triage-needed)

Attachments

(1 file)

The following test asserts on mozilla-central revision 8a59519e137e (options -m -n -a): var a = []; for (let j = 0; j < 5; ++j) { a.push(-2 in (a)); } S-s because this seems to be some length/offset guarding assertion in methodjit, so I'd assume this could go worse than just asserting.
Is this a regression?
Attached patch patchSplinter Review
It looks like this is due to bug 664824, so a recent regression. An unsigned comparison is being used (as is done for all other uses of guardArrayExtent) so behavior should be correct, I think this assert is bogus.
Assignee: general → bhackett1024
Attachment #593644 - Flags: review?
Group: core-security
Attachment #593644 - Flags: review? → review?(jdemooij)
Attachment #593644 - Flags: review?(jdemooij) → review+
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla13
Automatically extracted testcase for this bug was committed: https://hg.mozilla.org/mozilla-central/rev/efaf8960a929
Flags: in-testsuite+
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: