Closed Bug 461640 Opened 16 years ago Closed 15 years ago

Box objects should participate in cycle collection

Categories

(Core :: DOM: Core & HTML, defect)

defect
Not set
normal

Tracking

()

RESOLVED FIXED

People

(Reporter: peterv, Assigned: smaug)

References

Details

Attachments

(3 files, 1 obsolete file)

Attached patch v1 (obsolete) (deleted) — Splinter Review
Had this lying around, got reminded of it by the patch in bug 335998.
Reassigning this to smaug, since I'll use this to review the boxobject CC changes from the patch in bug 335998.
Assignee: peterv → Olli.Pettay
Blocks: strongparent
Attached patch v2 (deleted) — Splinter Review
These are changes copied from attachment 393225 [details] [diff] [review]. r+ if you address the comments below. -Please use NS_IMPL_CYCLE_COLLECTION_[0-4] where possible. -In general we try to keep the CC macros together and the QI/ADDREF/RELEASE together. Where possible, please keep NS_IMPL_CYCLE_COLLECTION_CLASS, unlink and traverse together (which should also undo the moving of AddRef/Release vs QI in some of the files).
Attachment #344747 - Attachment is obsolete: true
Attachment #395392 - Flags: review+
We should also do this, boxobjects hold properties which often end up holding JS objects. I didn't add unlinking in case something needs a property from a boxobject after it's unlinked, probably unlikely but I'm paranoid ;-).
Attachment #395393 - Flags: review?(Olli.Pettay)
Attachment #395393 - Flags: review?(Olli.Pettay) → review+
Attached patch v2 + comments (deleted) — Splinter Review
Status: ASSIGNED → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Component: DOM → DOM: Core & HTML
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: