Closed
Bug 99143
Opened 24 years ago
Closed 24 years ago
Memory leak of 72 bytes from 2 blocks allocated in xptiManifest::Read
Categories
(Core :: XPCOM, defect)
Tracking
()
VERIFIED
INVALID
Future
People
(Reporter: stephend, Assigned: dougt)
References
Details
(Keywords: helpwanted, memory-leak)
MLK: Memory leak of 72 bytes from 2 blocks allocated in
xptiManifest::Read(xptiInterfaceInfoManager *,xptiWorkingSet *)
Distribution of leaked blocks
72 bytes from 2 blocks of 36 bytes (first block: 0x041f46d8)
Allocation location
new(UINT)+0xc [new.cpp:23 ip=0x002da05c]
xptiManifest::Read(xptiInterfaceInfoManager *,xptiWorkingSet
*)+0xbd2 [c:\moz_src\mozilla\xpcom\reflect\xptinfo\src\xptiManifest.cpp:525
ip=0x10172dc2]
xptiInterfaceInfoManager::GetInterfaceInfoManagerNoAddRef(void)+0x204
[c:\moz_src\mozilla\xpcom\reflect\xptinfo\src\xptiInterfaceInfoManager.cpp:48
ip=0x10164a54]
XPTI_GetInterfaceInfoManager+0x29
[c:\moz_src\mozilla\xpcom\reflect\xptinfo\src\xptiInterfaceInfoManager.cpp:1613
ip=0x10170059]
NS_InitXPCOM2(nsIServiceManager * *,nsIFile
*,nsIDirectoryServiceProvider *)+0x1039
[c:\moz_src\mozilla\xpcom\build\nsXPComInit.cpp:400 ip=0x10020b19]
NS_InitXPCOM(nsIServiceManager * *,nsIFile *)+0x42
[c:\moz_src\mozilla\xpcom\build\nsXPComInit.cpp:259 ip=0x1001fac2]
main+0x2ec
[c:\moz_src\mozilla\xpfe\bootstrap\nsAppRunner.cpp:1632 ip=0x0040381c]
mainCRTStartup+0x3c2 [crtexe.c:338 ip=0x00432734]
| Assignee | ||
Updated•24 years ago
|
Keywords: helpwanted
Target Milestone: --- → Future
Comment 1•24 years ago
|
||
This is just a couple more object held by other objects. There is no root leak
here. In this case it is two xptiInterfaceInfo objects that are never released
because xpconnect is left with one XPCWrappedNative (wrapping a 'Components'
object) at shutdown. There is one interface info here representing nsISupports
and one representing nsIXPCComponents.
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → INVALID
Comment 3•23 years ago
|
||
*** Bug 132197 has been marked as a duplicate of this bug. ***
You need to log in
before you can comment on or make changes to this bug.
Description
•