Closed
Bug 111116
Opened 24 years ago
Closed 24 years ago
Memory leak of 116 bytes from 2 blocks allocated in nsMsgHeaderParser::ParseHeaderAddresses
Categories
(SeaMonkey :: MailNews: Message Display, defect)
Tracking
(Not tracked)
VERIFIED
INVALID
People
(Reporter: stephend, Assigned: mscott)
Details
(Keywords: memory-leak)
Build ID: Trunk pull @ 9:15 pm, 11/20/2001. Windows 2000.
Steps to Reproduce:
1. Log into an IMAP Inbox.
2. Read a bugmail.
3. Exit.
nsMsgHeaderParser::ParseHeaderAddresses
[W] MLK: Memory leak of 116 bytes from 2 blocks allocated in PR_Malloc
Distribution of leaked blocks
64 bytes from 1 block of 64 bytes (0x09cf9000)
52 bytes from 1 block of 52 bytes (0x094a2720)
Allocation location
malloc [msvcrt.DLL]
PR_Malloc [prmem.c:50]
nsMsgHeaderParser::ParseHeaderAddresses(char const*,char
const*,char * *,char * *,UINT *) [nsMsgHeaderParser.cpp:184]
XPTC_InvokeByIndex [xptcinvoke.cpp:152]
XPCWrappedNative::CallMethod
(XPCCallContext&,CallMode::XPCWrappedNative) [xpcwrappednative.cpp:2009]
XPC_WN_CallMethod(JSContext *,JSObject *,UINT,long *,long *)
[xpcwrappednativejsops.cpp:1266]
js_Invoke [jsinterp.c:832]
js_Interpret [jsinterp.c:2791]
js_Invoke [jsinterp.c:849]
nsXPCWrappedJSClass::CallMethod(nsXPCWrappedJS
*,WORD,nsXPTMethodInfo const*,nsXPTCMiniVariant *) [xpcwrappedjsclass.cpp:1216]
nsXPCWrappedJS::CallMethod(WORD,nsXPTMethodInfo
const*,nsXPTCMiniVariant *) [xpcwrappedjs.cpp:429]
SharedStub [xptcstubs.cpp:138]
nsMimeHtmlDisplayEmitter::WriteHTMLHeaders(void)
[nsMimeHtmlEmitter.cpp:231]
nsMimeHtmlDisplayEmitter::EndHeader(void)
[nsMimeHtmlEmitter.cpp:319]
MimeMessage_close_headers [mimemsg.cpp:405]
MimeMessage_parse_line [mimemsg.cpp:271]
convert_and_send_buffer [mimebuf.cpp:168]
mime_LineBuffer [mimebuf.cpp:255]
MimeObject_parse_buffer [mimeobj.cpp:255]
nsStreamConverter::OnDataAvailable(nsIRequest *,nsISupports
*,nsIInputStream *,UINT,UINT) [nsStreamConverter.cpp:919]
Reporter | ||
Updated•24 years ago
|
Reporter | ||
Updated•24 years ago
|
QA Contact: esther → stephend
Assignee | ||
Comment 1•24 years ago
|
||
I'm not fully convinced this is a real leak. JS owns this string and it should
be release during GC. Maybe we aren't running garbage collection before we shut
down the app...
Reporter | ||
Comment 2•24 years ago
|
||
rginda, always the man, in a discussion on IRC, told me to be very careful in
filing 'JS leaks'. I'm taking his word for it.
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → INVALID
Updated•21 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•