Closed Bug 463410 Opened 17 years ago Closed 17 years ago

Ranges should participate in cycle collection

Categories

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

defect

Tracking

()

RESOLVED FIXED
mozilla1.9.1b3

People

(Reporter: peterv, Assigned: smaug)

References

Details

(Keywords: fixed1.9.1)

Attachments

(2 files)

Attached patch v1Splinter Review
Spinning off from bug 335998, this is simply a general leak fix that we should do.
Attachment #346655 - Flags: superreview?(peterv)
Attachment #346655 - Flags: review?(peterv)
Comment on attachment 346655 [details] [diff] [review] v1 >diff --git a/content/base/src/nsRange.cpp b/content/base/src/nsRange.cpp >+NS_IMPL_CYCLE_COLLECTION_UNLINK_BEGIN(nsRange) >+ NS_IMPL_CYCLE_COLLECTION_UNLINK_NSCOMPTR(mStartParent) >+ NS_IMPL_CYCLE_COLLECTION_UNLINK_NSCOMPTR(mEndParent) This needs to call DoSetRange, I think.
Attachment #346655 - Flags: superreview?(peterv)
Attachment #346655 - Flags: superreview+
Attachment #346655 - Flags: review?(peterv)
Attachment #346655 - Flags: review+
Ah, true.
Attached patch v2Splinter Review
Calls reset, which calls DoSetRange with null/0 parameters.
Attachment #346658 - Flags: approval1.9.1?
Blocks: 448993
Note, this is needed for 1.9.1 for fix crasher bug 448993.
er, 'to fix', or something
Comment on attachment 346658 [details] [diff] [review] v2 a191=beltzner
Attachment #346658 - Flags: approval1.9.1? → approval1.9.1+
Should this not block, as well?
Flags: blocking1.9.1?
Sure.
Flags: blocking1.9.1? → blocking1.9.1+
Priority: -- → P2
Status: ASSIGNED → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
Whiteboard: [needs-1.9.1-landing]
Fixed on trunk and 1.9.1
Whiteboard: [needs-1.9.1-landing]
Keywords: fixed1.9.1
Target Milestone: --- → mozilla1.9.1b3
Component: DOM: Traversal-Range → DOM: Core & HTML
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: