Closed
Bug 96383
Opened 24 years ago
Closed 24 years ago
MLK: Memory leak of 128 bytes from 2 blocks allocated in orkinHeap::Alloc(nsIMdbEnv *,UINT,void * *)
Categories
(MailNews Core :: Database, defect)
Tracking
(Not tracked)
People
(Reporter: stephend, Assigned: Bienvenu)
Details
Build ID: 2001-08-21-09, Windows 2000, Purify.
MLK: Memory leak of 128 bytes from 2 blocks allocated in
orkinHeap::Alloc(nsIMdbEnv *,UINT,void * *)
Distribution of leaked blocks
128 bytes from 2 blocks of 64 bytes (first block: 0x09b81cc0)
Allocation location
new(UINT)+0xc [C:\WINNT\SYSTEM32\msvcrt.DLL ip=0x580039cb]
orkinHeap::Alloc(nsIMdbEnv *,UINT,void * *)+0x24
[c:\moz_src\mozilla\db\mork\src\orkinHeap.cpp:75 ip=0x0e3063d0]
orkinEnv::MakeEnv(morkEnv *,morkEnv *)+0x87
[c:\moz_src\mozilla\db\mork\src\orkinEnv.cpp:71 ip=0x0e30ace0]
nsMsgDatabase::OpenMDB(char const*,int)+0x8e
[c:\moz_src\mozilla\mailnews\db\msgdb\src\nsMsgDatabase.cpp:850 ip=0x0e5db71c]
nsImapMailDatabase::Open(nsIFileSpec *,int,int,nsIMsgDatabase *
*)+0x3f8 [c:\moz_src\mozilla\mailnews\db\msgdb\src\nsImapMailDatabase.cpp:99
ip=0x0e5d85dc]
nsMsgDatabase::OpenFolderDB(nsIMsgFolder *,int,int,nsIMsgDatabase *
*)+0xe7 [c:\moz_src\mozilla\mailnews\db\msgdb\src\nsMsgDatabase.cpp:832
ip=0x0e5db650]
nsImapMailFolder::UpdateImapMailboxInfo(nsIImapProtocol
*,nsIMailboxSpec *)+0x8d5
[c:\moz_src\mozilla\mailnews\imap\src\nsImapMailFolder.cpp:2230 ip=0x08bfd466]
XPTC_InvokeByIndex+0x75
[c:\moz_src\mozilla\xpcom\reflect\xptcall\src\md\win32\xptcinvoke.cpp:137
ip=0x100d1ac4]
EventHandler+0xb4
[c:\moz_src\mozilla\xpcom\proxy\src\nsProxyEvent.cpp:509 ip=0x100e2067]
md_EventReceiverProc+0x61
[c:\moz_src\mozilla\xpcom\threads\plevent.c:1071 ip=0x100cac26]
| Reporter | ||
Comment 1•24 years ago
|
||
Sorry about that, David. This is the same as bug 96379...
*** This bug has been marked as a duplicate of 96379 ***
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → DUPLICATE
Updated•21 years ago
|
Product: MailNews → Core
Updated•17 years ago
|
Product: Core → MailNews Core
You need to log in
before you can comment on or make changes to this bug.
Description
•