Closed Bug 82665 Opened 23 years ago Closed 4 years ago

Fix strong reference cycle between parser, sink, and document

Categories

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

Product:
Core
Component:
DOM: Core & HTML
Platform:
x86
Linux
Type:
defect

Tracking

()

Status:
RESOLVED WONTFIX
Milestone:
Future

People

(Reporter: nisheeth_mozilla, Unassigned)

Details

Currently, a parser -> sink -> document -> parser strong ref cycle prevents the
freeing of these objects for cases where document.write() is not followed up
with a document.close().

Fix this.
Target Milestone: --- → mozilla0.9.2
Updating QA contact to Shivakiran Tummala.
QA Contact: desale → stummala
Priority: -- → P1
Target Milestone: mozilla0.9.2 → mozilla0.9.3
Missed 0.9.3.
Target Milestone: mozilla0.9.3 → mozilla0.9.4
Bulk re-assign of my 0.9.4 bugs to Heikki.  I will not have the cycles to work
on these bugs while Clayton is on sabbatical for the next six weeks.
Assignee: nisheeth → heikki
Target Milestone: mozilla0.9.4 → mozilla0.9.5
Target Milestone: mozilla0.9.5 → mozilla0.9.6
Target Milestone: mozilla0.9.6 → mozilla0.9.8
Target Milestone: mozilla0.9.8 → Future
Component: DOM: HTML → DOM: Core & HTML
QA Contact: stummala → general
Severity: normal → major
Priority: P1 → P2

Is this still valid?

Priority: P2 → P3
Assignee: hjtoi-bugzilla → nobody

Now that we have the cycle collector, strong references are good. At least, I assume that's what this is about.

Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.