Closed
Bug 306598
Opened 19 years ago
Closed 6 years ago
nsGlobalWindow timeout code should use nsRefPtr<>s
Categories
(Core :: DOM: Core & HTML, defect, P5)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: mrbkap, Unassigned)
Details
Currently, nsGlobalWindow manages its list of timeouts using manual refcounting (calling AddRef() and Release() each time ownership changes). This is less than ideal because it becomes extremely easy to leak timeouts. We should instead use nsRefPtr<nsTimeout> to do the hard refcounting for us. The switch won't be entirely trivial, since nsRefPtr<> requires that Release not take any arguments and we'll have to determine the right structure to hold the queue of timeouts (would an nsDeque work? Or is there a better choice?).
Updated•15 years ago
|
Assignee: general → nobody
QA Contact: ian → general
Comment 1•6 years ago
|
||
https://bugzilla.mozilla.org/show_bug.cgi?id=1472046 Move all DOM bugs that haven't been updated in more than 3 years and has no one currently assigned to P5. If you have questions, please contact :mdaly.
Priority: -- → P5
| Reporter | ||
Comment 2•6 years ago
|
||
This was fixed at some point in the past 14 years.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WORKSFORME
| Assignee | ||
Updated•6 years ago
|
Component: DOM → DOM: Core & HTML
You need to log in
before you can comment on or make changes to this bug.
Description
•