Closed
Bug 720380
Opened 13 years ago
Closed 13 years ago
Assertion failure: lastProperty()->hasSlot() && getSlot(lastProperty()->slot()).isUndefined(), at jsscope.cpp:1056
Categories
(Core :: JavaScript Engine, defect)
Tracking
()
VERIFIED
FIXED
mozilla13
| Tracking | Status | |
|---|---|---|
| firefox11 | --- | verified |
| firefox12 | --- | verified |
| firefox-esr10 | 11+ | verified |
| status1.9.2 | --- | unaffected |
People
(Reporter: decoder, Assigned: bhackett1024)
Details
(Keywords: assertion, testcase, Whiteboard: [sg:critical][qa!] js-triage-done)
Attachments
(1 file)
|
1.36 KB,
patch
|
dvander
:
review+
johnath
:
approval-mozilla-aurora+
johnath
:
approval-mozilla-beta+
lsblakk
:
approval-mozilla-esr10+
|
Details | Diff | Splinter Review |
The following test asserts on mozilla-central revision 42368fe44c8c (options -m -n):
function MyObject( value ) {
this.toBoolean = (this[ this.Function = this ]++ );
}
new MyObject(true);
| Assignee | ||
Updated•13 years ago
|
Group: core-security
| Assignee | ||
Comment 1•13 years ago
|
||
When assignments to a property of 'this' are interleaved with other uses of 'this', information about all definite properties of objects created using that script need to be thrown out, as otherwise the definite slots found may be incorrect. A premature return in AnalyzeNewScriptProperties when a pushed value is popped in multiple places prevented this from happening.
Assignee: general → bhackett1024
Attachment #593666 -
Flags: review?(dvander)
| Assignee | ||
Comment 2•13 years ago
|
||
Comment on attachment 593666 [details] [diff] [review]
patch
[Approval Request Comment]
Regression caused by (bug #): TI
User impact if declined: potential vulnerability
Risk to taking this patch (and alternatives if risky): low, logic bug in rare situation
Attachment #593666 -
Flags: approval-mozilla-beta?
Attachment #593666 -
Flags: approval-mozilla-aurora?
Updated•13 years ago
|
Whiteboard: js-triage-needed → js-triage-needed [sg:?]
Updated•13 years ago
|
Attachment #593666 -
Flags: review?(dvander) → review+
| Assignee | ||
Comment 3•13 years ago
|
||
Updated•13 years ago
|
Target Milestone: --- → mozilla13
Comment 4•13 years ago
|
||
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Comment 5•13 years ago
|
||
Comment on attachment 593666 [details] [diff] [review]
patch
Discussed in triage, approved, but changes to JS always scare us - is there any way to QA for potential bustage this might introduce? Can we get it landed soon to maximize beta coverage?
Attachment #593666 -
Flags: approval-mozilla-beta?
Attachment #593666 -
Flags: approval-mozilla-beta+
Attachment #593666 -
Flags: approval-mozilla-aurora?
Attachment #593666 -
Flags: approval-mozilla-aurora+
| Assignee | ||
Comment 6•13 years ago
|
||
I don't think there's any real risk for bustage here, per comment 2 --- the code patterns it affects will not show up in realistic code, e.g. this[x]++ in a constructor.
https://hg.mozilla.org/releases/mozilla-aurora/rev/6b8c57dc160a
https://hg.mozilla.org/releases/mozilla-beta/rev/9f4a06e3fdb0
Updated•13 years ago
|
status-firefox11:
--- → fixed
status-firefox12:
--- → fixed
Comment 7•13 years ago
|
||
> User impact if declined: potential vulnerability
Setting sg:critical based on this.
Whiteboard: js-triage-needed [sg:?] → [sg:critical] js-triage-done
Comment 8•13 years ago
|
||
This bug should land on ESR as well.
status1.9.2:
--- → unaffected
status-firefox-esr10:
--- → affected
tracking-firefox-esr10:
--- → 11+
Comment 9•13 years ago
|
||
Comment on attachment 593666 [details] [diff] [review]
patch
Please land this today in time for tomorrow's go-to-build. See https://wiki.mozilla.org/Release_Management/ESR_Landing_Process for details and ping me or email release-mgmt@mozilla.com if there are any concerns about getting this landed in time.
Attachment #593666 -
Flags: approval-mozilla-esr10+
Comment 10•13 years ago
|
||
Quickly landed on ESR to meet the March 2 build date:
http://hg.mozilla.org/releases/mozilla-esr10/rev/081b50b02609
Comment 11•13 years ago
|
||
Verified fixed in Firefox 10.0.3esr.
Whiteboard: [sg:critical] js-triage-done → [sg:critical][qa+] js-triage-done
Comment 12•13 years ago
|
||
Verified fixed for Firefox 11.0b6 -- no assertion reproduced using test in comment 0 in js-shell built from today's mozilla-beta.
| Reporter | ||
Updated•13 years ago
|
Status: RESOLVED → VERIFIED
Comment 13•13 years ago
|
||
Verified fixed for Firefox 12 using 12b4-based js-shell.
Whiteboard: [sg:critical][qa+] js-triage-done → [sg:critical][qa!] js-triage-done
Updated•13 years ago
|
Group: core-security
| Reporter | ||
Comment 14•12 years ago
|
||
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.
Description
•