Closed
Bug 29356
Opened 25 years ago
Closed 24 years ago
leaking nsImapProtocol
Categories
(MailNews Core :: Backend, defect, P3)
MailNews Core
Backend
Tracking
(Not tracked)
VERIFIED
FIXED
M18
People
(Reporter: sspitzer, Assigned: jefft)
References
Details
(Keywords: memory-leak)
Attachments
(2 files)
we are leaking the nsImapProtocols now that I removed that bogus NS_RELEASE(me).
before we can fix this, we need to fix #29355
I'll post the refcount balance tree next.
Reporter | ||
Comment 1•25 years ago
|
||
here's are the refcount trees.
to reproduce, do this:
setenv XPCOM_MEM_REFCNT_LOG log-file.dat
setenv XPCOM_MEM_LOG_CLASSES nsImapProtocol
./mozilla -mail
perl -w ~/find-leakers.pl log-file.dat
perl -w ~/make-tree.pl --object 0x08684348 --ignore-balanced < ./log-file.dat >
~/imap-leak-1.txt
perl -w ~/make-tree.pl --object 0x087BB830 --ignore-balanced < ./log-file.dat >
~/imap-leak-2.txt
Reporter | ||
Comment 2•25 years ago
|
||
Reporter | ||
Comment 3•25 years ago
|
||
Reporter | ||
Comment 4•25 years ago
|
||
adding warren.
hmm, it looks like the nsThreads associated with nsImapProtocol are not getting
leaked.
Reporter | ||
Comment 5•25 years ago
|
||
adding david b to the cc list, in case he has cycles to help.
Comment 7•24 years ago
|
||
Mass moving M16 to M17 - look for nsbeta2 before anything else.
Target Milestone: M16 → M17
Reporter | ||
Comment 8•24 years ago
|
||
giving back to jefft.
cc'ing pavlov. he seems interested in this.
Assignee: sspitzer → jefft
Comment 9•24 years ago
|
||
Moving to M18 for the moment. Is this still happening? I've been told this has
been fixed.
Target Milestone: M17 → M18
Comment 10•24 years ago
|
||
I believe pav fixed this a couple months ago.
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
QA Contact: lchiang → stephend
I don't see this with the current run of Purify on my debug Win32 build.
Verified FIXED
Status: RESOLVED → VERIFIED
Updated•20 years ago
|
Product: MailNews → Core
Updated•16 years ago
|
Product: Core → MailNews Core
You need to log in
before you can comment on or make changes to this bug.
Description
•