Closed
Bug 58966
Opened 25 years ago
Closed 17 years ago
one-time leaks in nsLoggingService
Categories
(SeaMonkey :: General, defect, P3)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: dbaron, Assigned: cathleennscp)
References
Details
(Keywords: memory-leak, Whiteboard: [tind-mlk])
Attachments
(1 obsolete file)
nsLoggingService (and related code?) leak, once per session, an
nsObjectHashtable, an nsFileLogEventSink, a PRMonitor, and one nsLog object per
log. (The last of the 4 classes was removed from the leak stats so that this
wouldn't show up.)
Couldn't this leak be easily fixed by adding the necessary stuff to the
nsLoggingService::Release method. I do not right undertstand how to free the
mDefaultSink, but I believe it should be freed.
Reporter | ||
Comment 3•25 years ago
|
||
Why would deleting stuff in |Release| make sense?
I thought the problem here was that we're assigning things to statics and never
doing anything about them later on.
Updated•24 years ago
|
Assignee: dprice → asa
Component: XPCOM → Browser-General
QA Contact: kandrot → doronr
Comment 5•24 years ago
|
||
-> cathleen for a new home
Comment 6•24 years ago
|
||
adding cathleen so she'll know that you want her to find a new home for this bug.
Updated•21 years ago
|
Product: Browser → Seamonkey
Comment 9•17 years ago
|
||
Comment on attachment 23717 [details] [diff] [review]
patch
(In reply to comment #7)
> See bug 94480 (and the patch to remove this code).
This file was removed by bug 107510 :-)
Attachment #23717 -
Attachment is obsolete: true
Comment 10•17 years ago
|
||
R.Fixed.
David, reopen if I missed something.
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•