Closed
Bug 572232
Opened 14 years ago
Closed 14 years ago
js_InvokeConstructor with clampReturn==JS_TRUE and user-controlled ctor is a gc hazard
Categories
(Core :: JavaScript Engine, defect)
Core
JavaScript Engine
Tracking
()
RESOLVED
FIXED
People
(Reporter: Waldo, Assigned: Waldo)
References
Details
(Keywords: assertion, regression, testcase, Whiteboard: [sg:critical?][critsmash:investigating])
Attachments
(2 files)
615 bytes,
patch
|
dvander
:
review+
christian
:
approval1.9.2.9+
christian
:
approval1.9.1.12+
|
Details | Diff | Splinter Review |
1.51 KB,
patch
|
dvander
:
review+
|
Details | Diff | Splinter Review |
See bug 567577 comment 9 and bug 567577 comment 10.
I *think* we either need to add a tvr for the noted default-return object in js_InvokeConstructor or figure out whether __noSuchMethod__ functionality can ever be invoked in a constructing situation. The latter is probably hard, and the former is probably easy, which suggests probably the former is what we should do.
This also shows up in JS_New on trunk (but conservative stack scanning saves us) and in fun_applyConstructor (Narcissus-only, so I think we don't care), but neither of these cases needs a change.
Comment 1•14 years ago
|
||
Cc'ing mrbkap who was involved in bug 453462, and gal who took over at some point.
/be
Updated•14 years ago
|
Whiteboard: [sg:critical?]
Comment 2•14 years ago
|
||
this is still biting on branches, even if we get a conservative scanner on trunk, right?
Assignee | ||
Comment 3•14 years ago
|
||
Yes.
The patch in bug 567577 fixes this, I think.
Comment 5•14 years ago
|
||
(In reply to comment #4)
> The patch in bug 567577 fixes this, I think.
"Can we get a little more confidence than 'I Think'?" -- Damon Sicore
Comment 6•14 years ago
|
||
Waldo filed it. Waldo should decide. As far as I understand the bug report scanning the stack will find this root, so this is safe now. Waldo?
Assignee | ||
Comment 7•14 years ago
|
||
Comment 4 is correct with respect to trunk, even with conservative stack scanning turned off. We may not want to apply the patch there to branches exactly as is, however, as it does force clamping, which would be a web-visible change. Just adding the AutoObjectRooter (JSAutoTempValueRooter on branches) should be enough for branches, without compatibility concerns.
Comment 8•14 years ago
|
||
Waldo, could you please get a branch patch going?
Assignee: general → jwalden+bmo
Updated•14 years ago
|
Whiteboard: [sg:critical?] → [sg:critical?][critsmash:investigating]
Updated•14 years ago
|
status1.9.1:
--- → ?
status1.9.2:
--- → ?
Comment 10•14 years ago
|
||
Any news on the branch patch?
Assignee | ||
Comment 11•14 years ago
|
||
Attachment #460709 -
Flags: review?(dvander)
Updated•14 years ago
|
Attachment #460709 -
Flags: review?(dvander) → review+
Assignee | ||
Updated•14 years ago
|
Attachment #460709 -
Flags: approval1.9.2.9?
Attachment #460709 -
Flags: approval1.9.1.12?
Comment 12•14 years ago
|
||
Comment on attachment 460709 [details] [diff] [review]
Branch patch
a=LegNeato for 1.9.2.9 and 1.9.1.12. Please land on mozilla-1.9.2 default and mozilla-1.9.1 default.
Attachment #460709 -
Flags: approval1.9.2.9?
Attachment #460709 -
Flags: approval1.9.2.9+
Attachment #460709 -
Flags: approval1.9.1.12?
Attachment #460709 -
Flags: approval1.9.1.12+
Assignee | ||
Comment 13•14 years ago
|
||
http://hg.mozilla.org/releases/mozilla-1.9.1/rev/c54b6c62214d
http://hg.mozilla.org/releases/mozilla-1.9.2/rev/95e8deb0774b
Status: ASSIGNED → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Comment 14•14 years ago
|
||
Attachment #471885 -
Flags: review?
Updated•14 years ago
|
Attachment #471885 -
Flags: review? → review?(dvander)
Updated•14 years ago
|
Attachment #471885 -
Flags: review?(dvander) → review+
Updated•14 years ago
|
Group: core-security
Comment 15•12 years ago
|
||
Updated•12 years ago
|
Flags: in-testsuite+
You need to log in
before you can comment on or make changes to this bug.
Description
•