Closed
Bug 99145
Opened 24 years ago
Closed 24 years ago
Memory leak of 152 bytes from 2 blocks allocated in XPCNativeScriptableSharedMap::GetNewOrUsed
Categories
(Core :: XPConnect, defect)
Tracking
()
VERIFIED
INVALID
People
(Reporter: stephend, Assigned: dbradley)
References
Details
(Keywords: memory-leak)
MLK: Memory leak of 152 bytes from 2 blocks allocated in
XPCNativeScriptableSharedMap::GetNewOrUsed(UINT,char *,XPCNativeScriptableInfo *)
Distribution of leaked blocks
152 bytes from 2 blocks of 76 bytes (first block: 0x042dd990)
Allocation location
new(UINT)+0xc [new.cpp:23 ip=0x002da05c]
XPCNativeScriptableSharedMap::GetNewOrUsed(UINT,char
*,XPCNativeScriptableInfo *)+0x222
[c:\moz_src\mozilla\js\src\xpconnect\src\xpcmaps.cpp:597 ip=0x049af1b2]
XPCNativeScriptableInfo::Construct(XPCCallContext&,XPCNativeScriptableCreateInfo
const*)+0x3a3
[c:\moz_src\mozilla\js\src\xpconnect\src\xpcwrappednativejsops.cpp:1125
ip=0x049e7153]
XPCWrappedNativeProto::Init(XPCCallContext&,XPCNativeScriptableCreateInfo
const*)+0x76
[c:\moz_src\mozilla\js\src\xpconnect\src\xpcwrappednativeproto.cpp:89 ip=0x049eed66]
XPCWrappedNativeProto::GetNewOrUsed(XPCCallContext&,XPCWrappedNativeScope
*,nsIClassInfo *,XPCNativeScriptableCreateInfo const*,int)+0x601
[c:\moz_src\mozilla\js\src\xpconnect\src\xpcwrappednativeproto.cpp:213
ip=0x049ef906]
nsXPConnect::GetWrappedNativePrototype(JSContext *,JSObject
*,nsIClassInfo *,nsIXPConnectJSObjectHolder * *)+0x294
[c:\moz_src\mozilla\js\src\xpconnect\src\nsXPConnect.cpp:912 ip=0x0495d934]
nsWindowSH::GlobalResolve(nsISupports *,JSContext *,JSObject
*,JSString *,UINT,int *)+0x193e
[c:\moz_src\mozilla\dom\src\base\nsDOMClassInfo.cpp:2749 ip=0x08e9d6ce]
nsWindowSH::NewResolve(nsIXPConnectWrappedNative *,JSContext
*,JSObject *,long,UINT,JSObject * *,int *)+0x54b
[c:\moz_src\mozilla\dom\src\base\nsDOMClassInfo.cpp:2892 ip=0x08ea0f5b]
XPC_WN_Helper_NewResolve+0x61b
[c:\moz_src\mozilla\js\src\xpconnect\src\xpcwrappednativejsops.cpp:892
ip=0x049e9d1b]
js_LookupProperty+0xf8e [c:\moz_src\mozilla\js\src\jsobj.c:2139
ip=0x044de91e]
Reporter | ||
Updated•24 years ago
|
Comment 1•24 years ago
|
||
Are you really going to file bugs on all the leaf nodes of leaked memory?
We have better tools to show which objects are left unreachable and which are
simply entrained by other objects. The boehm collect tools beard wrote do this.
These objects are entrained by the xpcwrappednatives we leak at shutdown time.
At least one is a result of the Components object of the global object of the
xpc safe JSContext. It is better to look at leaked xpcwrappednative objects than
to focus on these leaf obejcts.
These are onetime shutdown leaks. I don't believe that it is safe to hack in
mechanisms to delete these objects since they are structs that the JS engine may
use after xpconnect is shutdown. These can only be safely removed if we are sure
that the shared JSRuntime is dead.
Reporter | ||
Comment 2•24 years ago
|
||
John, sorry. Since there's a better way of finding these, marking INVALID.
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → INVALID
Comment 4•23 years ago
|
||
*** Bug 111779 has been marked as a duplicate of this bug. ***
Comment 5•23 years ago
|
||
*** Bug 111780 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
•