222766 - mozilla memory usage grows incredibly high after long usage of browser

Status: RESOLVED INVALID

(SeaMonkey :: General, defect)

Description

[Brett Epps]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5) Gecko/20031007
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5) Gecko/20031007

Whenever I use Mozilla continually for a long time, or leave it running for
several hours, I find that the amount of memory it's using (determined using the
Windows Task Manager) has grown to enormous levels, sometimes as high as 80MB of
RAM.  Also, once it reaches this point, it crashes and I have to kill it with
Control-Alt-Delete.  This problem probably doesn't come up much, since I'm a bit
of a power user and I open many tabs at once.  Each tab adds to the amount of
memory used, but closing a tab doesn't lower the memory usage.

Reproducible: Always

Steps to Reproduce:
1. Open Mozilla
2. Open about 25-30 different sites in tabs
3. Click around, use browser for about two hours
4. Watch as memory grows
Actual Results:  
Mozilla crashed.

Expected Results:  
Supposedly it can handle "unlimited" tabs, therefore it shouldn't be crashing
after 25-30.  (The crash happens after most of those tabs have already been
closed, anyway.)

My system:
Intel Pentium III 533 Mhz
384 MB SDRAM
4 MB Integrated Intel Graphics (sad)
Windows XP Home (Fully Updated)
20 GB ATA-100 Hard Drive (Windows lies on a 12 GB partition, with about 5 GB free.)

I am using the Modern theme.

Comment 1

[Christian Hamacher]

I'm quite sure there are about a hundred duplicates of this bug already -
especially, since this one does not contain any useful sequence of events or
detailed activities to reproduce *a distinct* memory leak, it's most likely INVALID.

Comment 2

[Boris Zbarsky [:bzbarsky]]

Indeed.  Please reopen if you have a set of steps that show a memory leak (and
memory increasing in Task Manager does not constitute a memory leak, since Task
Manager unfortunately includes memory that the process has deallocated but the
system allocator has cached....)