Closed
Bug 87241
Opened 24 years ago
Closed 21 years ago
Possible Leak in nsParser?
Categories
(Core :: DOM: HTML Parser, defect, P4)
Core
DOM: HTML Parser
Tracking
()
RESOLVED
FIXED
Future
People
(Reporter: Deinst, Assigned: harishd)
Details
Attachments
(1 file)
|
516 bytes,
patch
|
Details | Diff | Splinter Review |
I can't convince myself that it is possible to trigger this, but I can't
convince myself that it isnt.
|
Reporter | |
Comment 1•24 years ago
|
||
David: Do you have a url or testcase that could reporduce this leak?
|
|
Reporter | |
Comment 3•24 years ago
|
||
No, Sorry. I don't even know if it is possible to trigger, as there are many
calls to parse that do not register an observer at all. I am fairly certain
that if parse is called twice on the same parser and the first call registered a
listener then that listener will dissapear.
Setting to FUTURE for now. Let's put it back on the radar if we hit a real case.
Priority: P1 → P4
Target Milestone: mozilla0.9.3 → Future
|
|
||
Comment 5•21 years ago
|
||
This got fixed by the changes in bug 40149
Status: ASSIGNED → RESOLVED
Closed: 21 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•