Closed Bug 605380 Opened 15 years ago Closed 15 years ago

Memory usage growing for no reason

Categories

(Firefox :: General, defect)

3.6 Branch
x86_64
Windows 7
defect
Not set
major

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: marak.v1, Unassigned)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-GB; rv:1.9.2.10) Gecko/20100914 Firefox/3.6.10 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-GB; rv:1.9.2.10) Gecko/20100914 Firefox/3.6.10 Since the last update, even sitting idle, the memory usage of firefox has been climbing. It reach's a point(somewhere over 1.4 million K) when firefox becomes instable, and begins to artifact webpages(repeating paragraph long sections when attempting to scroll down) requiring a restart. If left too long, the firefox process will remain(and continue to grow) in process's, but no application heading(ending the process fix's this). It happens even when viewing offline files with no outside stimulis(its university offline files, so no add's or anything). Getting bloody annoying lol, even sitting here atm doing this its grown from 350,000k to just under 500,000k Reproducible: Always Steps to Reproduce: 1.Open firefox and at least 2 tabs(probably even one tab, have not confirmed) 2. 3. only addon is ABP(Add block plus) - disabling this does not stop the problem. Had script block on a few days ago, but removed as it was causing more instability.
Can you test in a fresh profile? http://support.mozilla.com/en-US/kb/managing+profiles Also, update flash, java, quicktime, adobe reader, etc. to the latest version available on the developers websites. When you have it sitting idle, is a webpage open? What is a list of the webpages you visited before?
Version: unspecified → 3.6 Branch
Alright, doing all that now(gotta pick up the missus in 30 mins though), ill post back here once its done
Today's patch fixed the problem - go firefox team!
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Resolution: FIXED → WORKSFORME
You need to log in before you can comment on or make changes to this bug.