Michael Kraft [:morac] Reporter
	Description • 19 years ago

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b5) Gecko/20051012 Firefox/1.4.1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b5) Gecko/20051012 Firefox/1.4.1

There is a memory leak on unloading pages that is very easy to duplicate.

The leak occurs even with no extensions installed in a brand new profile in
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b5) Gecko/20051012
Firefox/1.4.1

Installing certain extensions seems to make it much worse.  For example using
the Roboform adapter firefox extensions causes memory usage to skyrocket very
quickly (though this may be a bug in the roboform extension).

Reproducible: Always

Steps to Reproduce:
1. Open browser and go to www.cnn.com
2. Go to www.netscape.com in the same tab.
3. Use back and forward arrows to go back and forth between the two pages.

Actual Results:  
The memory usage slowly goes up every time the browser goes from cnn to netscape
and back.  There does not appear to be a maximum so the memory usage will keep
going up until there is no memory left.  I have seen firefox.exe using 250 MB of
memory with every tab closed and nothing in the memory cache. 

Expected Results:  
memory usage should remain relatively constant.

	Adam Guthrie
	Comment 1 • 19 years ago

I'm pretty sure this is due to the pages in bfcache getting pushed into the
memory. This is controlled with browser.sessionhistory.max_total_viewers which
is set to -1 by default (caches pages based on available memory). Could you test
this with browser.sessionhistory.max_total_viewers set to zero (bfcache off) and
see if this still occurs? 

	Michael Kraft [:morac] Reporter
	Comment 2 • 19 years ago

I tried repeating the steps with browser.sessionhistory.max_total_viewers set to
0 and got the same results.

	Daniel Veditz [:dveditz]
	Comment 3 • 19 years ago

I saw memory use go up a little the first couple of back and forths, but then it seemed to plateau (bfcache turned off).

	Steve England [:stevee]
	Comment 4 • 19 years ago

Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9a1) Gecko/20060115 Firefox/1.6a1 ID:2006011506
I can't see any leakage with leak-gauge.pl with a new profile and going back/forward between cnn.com and netscape.com

	Steve Chapel
	Comment 5 • 19 years ago

I tried on Windows XP with the 20060120 trunk build of Firefox with a new profile and the 20060119 trunk build of SeaMonkey with a well-worn profile. I saw a memory increase at first, but memory usage quickly leveled off. Leak gauge reports no leaks.

	Mike Schroepfer
	Comment 6 • 18 years ago

Clearing dep on 320915