Closed Bug 97509 Opened 23 years ago Closed 23 years ago

MLK: Memory leak of 18048 bytes from 282 blocks allocated in NSGetModule

Categories

(SeaMonkey :: MailNews: Address Book & Contacts, defect)

x86
Windows 2000
defect
Not set
normal

Tracking

(Not tracked)

VERIFIED INVALID

People

(Reporter: stephend, Assigned: Bienvenu)

Details

(Keywords: memory-leak)

Saw this using Purify on Windows 2000, with a fresh (11 am) opt moz cvs pull.

MLK: Memory leak of 18048 bytes from 282 blocks allocated in NSGetModule
[W] MLK: Memory leak of 18048 bytes from 282 blocks allocated in NSGetModule
        Distribution of leaked blocks
        Allocation location
            new(UINT)+0xc        [C:\WINNT\SYSTEM32\msvcrt.DLL ip=0x580039cb]
            NSGetModule+0x19ab  
[C:\moz_src\mozilla\dist\WIN32_O.OBJ\bin\components\mork.dll ip=0x0d222a05]
            NSGetModule+0x12fce 
[C:\moz_src\mozilla\dist\WIN32_O.OBJ\bin\components\mork.dll ip=0x0d234028]
            nsProxyObjectCallInfo::=(nsProxyObjectCallInfo const&)+0x4a58
[C:\moz_src\mozilla\dist\WIN32_O.OBJ\bin\components\addrbook.dll ip=0x07f12a8d]
            nsProxyObjectCallInfo::=(nsProxyObjectCallInfo const&)+0x1592
[C:\moz_src\mozilla\dist\WIN32_O.OBJ\bin\components\addrbook.dll ip=0x07f0f5c7]
            nsProxyObjectCallInfo::=(nsProxyObjectCallInfo const&)+0x13e6
[C:\moz_src\mozilla\dist\WIN32_O.OBJ\bin\components\addrbook.dll ip=0x07f0f41b]
            nsProxyObjectCallInfo::=(nsProxyObjectCallInfo const&)+0xc4f
[C:\moz_src\mozilla\dist\WIN32_O.OBJ\bin\components\addrbook.dll ip=0x07f0ec84]
            nsProxyObjectCallInfo::=(nsProxyObjectCallInfo const&)+0xa9af
[C:\moz_src\mozilla\dist\WIN32_O.OBJ\bin\components\addrbook.dll ip=0x07f189e4]
            nsGetInterface::=(nsGetInterface const&)+0x8eb5
[C:\moz_src\mozilla\dist\WIN32_O.OBJ\bin\components\addrbook.dll ip=0x07f0a8fa]
            nsGetInterface::=(nsGetInterface const&)+0x92fa
[C:\moz_src\mozilla\dist\WIN32_O.OBJ\bin\components\addrbook.dll ip=0x07f0ad3f]
Blocks: 92580
leak bugs / qacontact --> me.
QA Contact: fenella → stephend
taking - however, I don't think this stack trace is useful. What operations did
you perform to get this leak? Also, it looks like you haven't got any symbols in
mork, which is why the stack trace is not useful. I've seen stack traces from
mork in other reports, so I think there is stack trace information available
(i.e., everything isn't static).
Assignee: chuang → bienvenu
Launching mozilla.exe -compose, typing stephe (letting it search from a local 
addressbook for <stephend@netscape.com>, moving the selection down 3 times to 
highlight the above email address, hitting return 3 times, typing nothing in 
the message body, nothing in the subject, and simply hitting OK to send the 
dialog.

this isn't useful, but I'm on top of a bunch of address book leaks, so I don't
think we need to worry about this.
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → INVALID
Yeah, sorry, looks bogus to me, too.

Verified.
Status: RESOLVED → VERIFIED
No longer blocks: 92580
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.