87482 - opening newsgroup and closing mail/news window leaks mem

Status: RESOLVED INCOMPLETE

(MailNews Core :: Backend, defect)

Description

[Greg Miller]

I started up 2001062204 on NT4sp6a. Task manager showed 18MB usage. I opened the
mail window and TM showed 24MB. I selected netscape.public.mozilla.general and
memory usage rose to 40MB. I then closed the mail/news window (leaving only the
original browser window with about:blank open), cutting memory usage by about 400k.

16MB seems like a lot to lose to fragmentation... Could this be another circular
reference? Or is there some other reason memory usage isn't dropping back more
significantly?

Comment 1

[Greg Miller]

I did some more experiments... It appears that the mail and news client isn't
leaking the bulk of the memory (closing the window, reopening it, and selecting
the newsgroup again doesn't increase the memory usage by much), but it doesn't
appear to ever release the memory used by messages in folders I've viewed during
the current session.

Also note that the 16MB memory used by n.p.m.general on my system is entirely
with previously read messages that aren't displayed. I thought I remembered
someone indicating that the mail/news perf branch that landed in 0.9 would avoid
loading messages that wouldn't appear in the listing.

Comment 2

[[e-mail] (gone - use [e-mail] instead)]

This sounds very close to bug 93013, where we are leaking tons of memory,
depending on the size of the newsgroup.  Greg, if you agree, I'll mark it a DUP.

Comment 3

[Greg Miller]

Bug 64868 is more specific and seems to be the root cause... but there seem to
be several bugs on issues with mail/news failing to release its memory usage.

Comment 4

[[e-mail] (gone - use [e-mail] instead)]

okay, see also bug 96382 and bug 97020.  I'll leave this one open to be sure and
catch as many cases as possible.

Comment 5

[Dan]

I'm still seeing huge leaks in mailnews, unfortunately. Just browsing through 20
something newsgroups leaves Mozilla using 63.5M RSS (Mozilla 1.4beta on Redhat 9).

Memory usage seems to go up 1-5M everytime a new group is opened, and never goes
down.

Comment 6

[Wayne Mery (:wsmwk)]

really nothing measurable here and no steps to reproduce.
there are other bugs which better address the issue(s).
closing incomplete