Closed
Bug 13615
Opened 25 years ago
Closed 24 years ago
MLK: nsInterfaceInfoManager::initInterfaceTables()
Categories
(Core :: XPCOM, defect, P3)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: bruce, Assigned: mike+mozilla)
References
Details
(Keywords: memory-leak)
nsInterfaceInfomanager::initInterfaceTables() leaks an nsDirectoryIterator, or
doesn't ever tell the nsDirectoryIterator to close the directory?
This is showing up in Purify as as a leaked file descriptor. Current build from
September 11, 1999 on Solaris.
Updated•25 years ago
|
Assignee: jband → mccabe
Component: XPConnect → xpidl
Comment 1•25 years ago
|
||
Thanks for the report!
Reassigning to mccabe. IIM is his.
Assignee | ||
Updated•25 years ago
|
Status: NEW → ASSIGNED
Assignee | ||
Comment 2•25 years ago
|
||
My bug.
Comment 3•25 years ago
|
||
how big is the leak
Comment 4•25 years ago
|
||
I'm not sure how big the leak is.
But, nsInterfaceInfomanager::initInterfaceTables is called only once. And the
only nsDirectoryIterator is an automatic variable -
http://lxr.mozilla.org/seamonkey/source/xpcom/reflect/xptinfo/src/nsInterfaceInf
oManager.cpp#345 - that ought to be cleaning itself up in its own dtor. A quick
look at the implementations -
http://lxr.mozilla.org/seamonkey/ident?i=~nsDirectoryIterator - seems to
indicate that they are trying to clean themselves up.
Is this perhaps Purify confusion or a nsDirectoryIterator bug?
Comment 5•25 years ago
|
||
what does purify report? I do not see this on NT. However, the unix
implementation does close the directory when the destructor is called:
http://lxr.mozilla.org/seamonkey/source/xpcom/io/nsFileSpecUnix.cpp#543
could purify be confused about the declaration of the nsDirectoryIterator in
the for-loop?
Comment 6•24 years ago
|
||
I've surfed several sites and do not leak an nsDirectoryIteratorImp on a
current Linux build.
Assignee | ||
Comment 7•24 years ago
|
||
Marking as WORKSFORME, based on the last two reports.
Thanks!
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•