Closed
Bug 1160567
Opened 10 years ago
Closed 10 years ago
Assert that we do not have any Object subclasses flowing through generic GCMethods
Categories
(Core :: JavaScript: GC, defect)
Core
JavaScript: GC
Tracking
()
RESOLVED
FIXED
mozilla40
Tracking | Status | |
---|---|---|
firefox40 | --- | fixed |
People
(Reporter: terrence, Assigned: terrence)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
2.62 KB,
patch
|
jonco
:
review+
|
Details | Diff | Splinter Review |
I should have done this when I added the JSFunction overload, but didn't want to make the bug that obvious in the checkin. We should be good now though, so let's get that assertion in place.
Filing as sec-sensitive until the try results are back, just incase.
Assignee | ||
Comment 1•10 years ago
|
||
Comment on attachment 8600381 [details] [diff] [review]
forward_security_on_object_exposure-v0.diff
Try run seems to be green.
Attachment #8600381 -
Flags: review?(jcoppeard)
Comment 2•10 years ago
|
||
Comment on attachment 8600381 [details] [diff] [review]
forward_security_on_object_exposure-v0.diff
Review of attachment 8600381 [details] [diff] [review]:
-----------------------------------------------------------------
Nice.
Attachment #8600381 -
Flags: review?(jcoppeard) → review+
Assignee | ||
Comment 3•10 years ago
|
||
Assignee | ||
Comment 4•10 years ago
|
||
Try is green -- as I thought, there are no Object subclasses other than Function we need to handle explicitly in barriers.
Group: core-security
Comment 6•10 years ago
|
||
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla40
You need to log in
before you can comment on or make changes to this bug.
Description
•