25698 - increased memory usage (memory leaks?) after browsing for period of time

Status: VERIFIED INVALID

(SeaMonkey :: General, defect, P3)

Description

[crisrita]

This might be important to some users.
Mozilla is a ram-hog.
I have 65 Mb of ram, and about 25 minutes of browsing on Mozilla eats it all up.
Please try to fix this.

Comment 1

[Myk Melez [:myk] [@mykmelez]]

Although this bug was originally sparse on documentation, it has potential to be
a good catch-all for leak bugs.  In other words, make this bug depend on all the
significant leak bugs, and then it can be used to track progress on eliminating
leaks.

Here's what information I can add to the leak question: On my Celeron RedHat
Linux 6.0 machine with 128mb physical and 128mb virtual memory, Mozilla
2000-01-25-20 (M13) starts up using 17-18mb memory.  After a recent session of
extensive browsing and using mail (along with an extensive period of doing
nothing with my computer), Mozilla was using around 33-34mb memory.

This bug could possibly be a duplicate of bug 11935, but that bug is about
Mozilla being a memory hog, not a memory leaker.  In other words it talks about
Mozilla using too much memory right from the start as opposed to using more
memory over time.

Bug 17591 is a webshell leak bug.  I suspect that this bug depends on that one,
although they probably aren't duplicates unless the webshell is the only thing
causing leaking in Mozilla.

I am adding bug 17591 as a duplicate of this bug and changing the os to all
since I can duplicate this on Linux.

Comment 2

[Sean Richardson]

The last time I used Mozilla on Win95 for any length of time, back in 1999 11,
it would within 20 minutes eat up almost all the memory, although that memory
could be released for use by other apps. On WinNT, Mozilla usually grows
slowly to 25-30MB with use. So while this is an XP problem, it may show worse
on some OS than on others.

Comment 3

[leger]

Moving all open "[e-mail]" assignee bugs to "[e-mail]" to 
review.

Comment 4

[Ross Brackett]

This is silly.  There have been plenty of "Mozilla slowly eats more and more 
memory but I won't tell you anything more" bugs, all the way back to bug 284.  
Marking INVALID.

Comment 5

[Blake Ross]

*spam* changing qa contact from [e-mail] to me ([e-mail]) 
on 121 open or resolved (but not verified) bugs.  sorry for the spam everybody, 
but most of these bugs would just remain dormant and not checked by QA 
otherwise.  I'm not sure how so many bugs have nobody as their QA contact, but 
I suspect this is the fault of some sort of bugzilla corruption that happened 
at some point (most of these bugs are in the 20000-26000 range, and I don't see 
where in the activity log that QA contact explicitly changed to 
[e-mail])

Anyways, sorry again for spam.  If you really get annoyed, I'm usually 
available in #mozilla on IRC for torture.

Comment 6

[leger]

There are many memory leak bugs.  Query for open "mlk" keyword bugs and you'll 
see all 81 of them today :-)  marking Verified.