580895 - Reverse Memory leak? / Garbage collection out of control??

Status: RESOLVED INCOMPLETE

(Firefox :: General, defect)

Description

[Danial Horton]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 6.1; en-GB; rv:1.9.2.7) Gecko/20100713 Firefox/3.6.7 GTB7.1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-GB; rv:1.9.2.7) Gecko/20100713 Firefox/3.6.7 GTB7.1

After updating to 3.6.7 i noticed that firefox is alot slower when switching tabs and loading pages.

Opening up Task manager i noticed that Commit size is almost always larger than the Working sets, and that the working sets are actually decreasing by 1MB every 1-2 seconds until it reaches 200ish MB's where it stabilises. This is not the behavior i had with 3.6.6, where worksets would only reduce after forcing a paging operation (such as launching a memory hungry game).

Reproducible: Always

Steps to Reproduce:
Load a bunch of different sites and watch the working sets continually decrease
Actual Results:  
the working set decreased continually, without effecting the commit size making firefox feel clunky and slow.

Expected Results:  
Firefox to manage memory properly.

Comment 1

[Tyler Downer [He/Him]]

Please create a new profile and test there. http://support.mozilla.com/en-US/kb/Managing+profiles Also update your quicktime, flash, java, etc.

Comment 2

[Wayne Mery (:wsmwk)]

Danial, did you get this sorted out?

 (In reply to comment #1)
> Please create a new profile and test there.
> http://support.mozilla.com/en-US/kb/Managing+profiles Also update your
> quicktime, flash, java, etc.

Comment 3

[Danial Horton]

I found the cause to be updating graphics drivers while firefox was openened.

a reboot always resolved the problem, I've since taken to logging off/on prior to updating drivers to prevent any potential issues.

Comment 4

[Stephanie Daugherty [:sdaugherty]]

(In reply to comment #3)
> I found the cause to be updating graphics drivers while firefox was openened.
> 
> a reboot always resolved the problem, I've since taken to logging off/on 
prior to updating drivers to prevent any potential issues.

Interesting. I wouldn't have thought to ask about this as a cause of 
instability.

Comment 5

[Marco Castelluccio [:marco]]

Can we close this bug now?

Comment 6

[Wayne Mery (:wsmwk)]

(In reply to Marco Castelluccio from comment #5)
> Can we close this bug now?

there may be an underlying problem, but I don't think we have enough info to investigate further. From that perspective => incomplete

Comment 7

[Danial Horton]

indeed, there could still be something there, i haven't reproduced it since changing to shutting off firefox before updating the display drivers, but its still a little odd that firefox is the only one that starts doing this especially when i don't have acceleration enabled (firefox vram usage inteferes with gaming)