474541 - FF 3.0.5 will consume more than 300mb of RAM within 18 minutes of use.

Status: RESOLVED INCOMPLETE

(Firefox :: General, defect)

Description

[Adam West]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.5) Gecko/2008120122 Firefox/3.0.5
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.5) Gecko/2008120122 Firefox/3.0.5

When using Firefox, especially with multiple windows (sometimes tabs), the program consumes >300MB of memory. Additionally, sometimes the window will freeze and the connection will go out, indicating that FF has surpassed 400MB.

Reproducible: Always

Steps to Reproduce:
1. Open FF
2. Open another window
3. In one window only, open multiple tabs, with multimedia embedded or instant messaging (meebo specifically)
4. Take note of Firefox's greedy RAM usage. 
Actual Results:  
RAM + Virtual RAM levels jet past 300MB, sometimes even reaching >600M!! I have 512 RAM!

Expected Results:  
The software should have leveled out at some point, perhaps around 64M - 128M (that is on the requirements page)

I have a Dell Dimension 3000, w/ all the trash that comes w/ old Dells:
-Win XP HE
-512 RAM
-P4
-80G HDD

I have no other browser, and I like Firefox, so this should be addressed ASAP

Comment 1

[Matthias Versen [:Matti]]

Do you get this in the Firefox safemode ?
http://support.mozilla.com/en-US/kb/Safe+Mode

If yes; 
Please provide exact steps to reproduce including every used URL and link

Comment 2

[Tyler Downer [He/Him]]

This is a mass search for bugs which are in the Firefox General component, are
UNCO, have not been changed for 500 days and have an unspecified version. 

Reporter, can you please update to Firefox 3.6.10 or later, create a fresh profile, http://support.mozilla.com/en-US/kb/managing+profiles, and test again. If you still see the issue, please update this bug. If the issue is gone, please set the status to RESOLVED > WORKSFORME.

Comment 3

[Tyler Downer [He/Him]]

No reply from reporter, INCOMPLETE. Please retest with Firefox 3.6.12 or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.