Closed
Bug 591426
Opened 16 years ago
Closed 15 years ago
"Assertion failure: non-global object at end of scope chain," with sharps, __defineSetter__
Categories
(Core :: JavaScript Engine, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 612836
| Tracking | Status | |
|---|---|---|
| blocking2.0 | --- | final+ |
People
(Reporter: gkw, Unassigned)
References
Details
(Keywords: assertion, regression, testcase)
wrap.call(__defineSetter__("",function(){}),#0=*)
asserts js debug shell on TM changeset aef91431ff40 without -j at Assertion failure: non-global object at end of scope chain, at ../jsobj.cpp:6116
| Reporter | ||
Updated•16 years ago
|
Summary: "Assertion failure: non-global object at end of scope chain," → "Assertion failure: non-global object at end of scope chain," with sharps, __defineSetter__
| Reporter | ||
Updated•16 years ago
|
blocking2.0: --- → ?
| Reporter | ||
Comment 1•16 years ago
|
||
autoBisect shows this is probably related to the following changeset:
The first bad revision is:
changeset: 43356:d770ef6237ea
user: Jason Orendorff
date: Wed Jun 16 16:13:28 2010 -0500
summary: Bug 570169 - Part 2, add assertions that gcthings do not leak across compartments. r=gal.
Blocks: 570169
Updated•16 years ago
|
blocking2.0: ? → final+
Comment 2•15 years ago
|
||
This now asserts like so:
Assertion failure: parent, at ../jswrapper.cpp:304
Comment 3•15 years ago
|
||
(In reply to comment #2)
> This now asserts like so:
>
> Assertion failure: parent, at ../jswrapper.cpp:304
Which makes it look a lot like bug 612836.
Comment 4•15 years ago
|
||
And if I apply the (not yet landed) patch from bug 612836 the test in comment 0 no longer asserts.
Updated•15 years ago
|
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → DUPLICATE
Comment 6•13 years ago
|
||
A testcase for this bug was already added in the original bug (bug 612836).
Flags: in-testsuite-
You need to log in
before you can comment on or make changes to this bug.
Description
•