Closed
Bug 701227
Opened 13 years ago
Closed 13 years ago
"Assertion failure: (obj)->propertyCount() == 1,"
Categories
(Core :: JavaScript Engine, defect)
Tracking
()
VERIFIED
FIXED
mozilla11
Tracking | Status | |
---|---|---|
firefox10 | --- | verified |
People
(Reporter: gkw, Assigned: luke)
References
Details
(4 keywords, Whiteboard: js-triage-done [qa!])
Attachments
(2 files)
6.33 KB,
text/plain
|
Details | |
1.45 KB,
patch
|
Waldo
:
review+
asa
:
approval-mozilla-aurora+
|
Details | Diff | Splinter Review |
String((function() {
try {} catch (d) {
let x
}
}), "\
try {} catch (d) {\
let x\
}\
")
asserts js debug shell on m-c changeset 4fb61ebbf8ff with patch v1 from bug 697279 without any CLI arguments at Assertion failure: (obj)->propertyCount() == 1,
autoBisect shows this is probably related to the following changeset:
The first bad revision is:
changeset: 79903:a6c390aa3bf2
user: Luke Wagner
date: Mon Nov 07 11:46:25 2011 -0800
summary: Bug 696813 - Simplify Decompile (r=waldo)
Assignee | ||
Comment 1•13 years ago
|
||
Of course let decl in a catch appends to the catch's block!
Assignee: general → luke
Attachment #573398 -
Flags: review?(jwalden+bmo)
Updated•13 years ago
|
Attachment #573398 -
Flags: review?(jwalden+bmo) → review+
Assignee | ||
Comment 2•13 years ago
|
||
Comment on attachment 573398 [details] [diff] [review]
fix
Low-risk fix; causes safe crash if exercised.
Attachment #573398 -
Flags: approval-mozilla-aurora+
Assignee | ||
Updated•13 years ago
|
Attachment #573398 -
Flags: approval-mozilla-aurora+ → approval-mozilla-aurora?
Assignee | ||
Updated•13 years ago
|
Whiteboard: js-triage-needed → js-triage-done
Assignee | ||
Comment 3•13 years ago
|
||
Target Milestone: --- → mozilla11
Comment 4•13 years ago
|
||
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Updated•13 years ago
|
Attachment #573398 -
Flags: approval-mozilla-aurora? → approval-mozilla-aurora+
Assignee | ||
Comment 5•13 years ago
|
||
Assignee | ||
Updated•13 years ago
|
status-firefox10:
--- → fixed
Hi guys.
Can you please tell me how can I verify this bug?
Thanks.
Assignee | ||
Comment 7•13 years ago
|
||
Comment 8•13 years ago
|
||
I used the beta source with the latest revision (mozilla-beta-226c1a05e0b6) and built the js debug shell; then I run the test from comment #0 and no message was displayed.
Is this what was needed to verify this issue?
Thanks!
Comment 9•13 years ago
|
||
(In reply to Mihaela Velimiroviciu [QA] from comment #8)
> I used the beta source with the latest revision (mozilla-beta-226c1a05e0b6)
> and built the js debug shell; then I run the test from comment #0 and no
> message was displayed.
> Is this what was needed to verify this issue?
> Thanks!
I used Mac OS X 10.6
Updated•13 years ago
|
Status: RESOLVED → VERIFIED
Keywords: verified-beta
Whiteboard: js-triage-done [qa+] → js-triage-done [qa!]
Comment 10•12 years ago
|
||
A testcase for this bug was automatically identified at js/src/jit-test/tests/basic/testBug701227.js.
Flags: in-testsuite+
You need to log in
before you can comment on or make changes to this bug.
Description
•