Closed Bug 12114 Opened 25 years ago Closed 25 years ago

[mlk] nsBookmarksService leaks

Categories

(Core Graveyard :: RDF, defect, P3)

x86
Windows NT
defect

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: waterson, Assigned: mozilla)

References

Details

Attachments

(1 file)

The tree widget, with content generated from an RDF datasource, leaks the datasource.
Blocks: 11413
Status: NEW → ASSIGNED
Target Milestone: M10
Attached file test case (save as leak.xul) (deleted) —
To reproduce, download above test case. 1. Run viewer. 2. Set breakpoint in nsBookmarksService::~nsBookmarksService(). 3. Open test case. 4. Click "Back" button. Expectation is that nsBookmarksService() will be destroyed. It isn't.
Urgh. Here's what is happening. The RDF service acquires datasources using the XPCOM service manager. The XPCOM service manager holds on to the component UNTIL XPCOM SHUTS DOWN. This seems evil to me, but I'm not aware of all the issues. See this thread: news://news.mozilla.org/37BB6D29.451B220F%40netscape.com
how big do we think this leak is?
Blocks: 14516
Target Milestone: M11 → M12
bulldozer to M12
Summary: [mlk] tree widget with generated content leaks datasource → [mlk] nsBookmarksService leaks
this is a different bug now, and i think the leak is happening because of the extra addref that we do to keep the bookmarks service alive for the timer callback.
Assignee: waterson → rjc
Status: ASSIGNED → NEW
robert, i'm gonna give you this love. it's the timer-leaking-bookmarks thingy.
Status: NEW → ASSIGNED
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Fixed. Instead of doing an extra refcnt for the nsBookmarksService in the timer, we now simply cancel the timer in the nsBookmarksService DTOR.
Status: RESOLVED → VERIFIED
marking verified
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: