Firefox acting up again

[»1587200]

After the upgrade to 2.0.0.2 it seems that Firefox is eating more memory than usual (around 98mb) and chomping on way too much CPU power. Every time I type or move my mouse over my FF window, my CPU spikes to 70%+ until I stop.

 

Anyone else noticing anything simliar with FF?

[Dav]

I will test when i get home but from the feel of the system it seems to be normal.

[»Maverick]

Works fine for me.

Already ruled out the add-ons you have installed?

[rootbear75]

pretty sure it works fine on mine also... i check when i get home

 

How do you check the version?

 

but from what i see know... it works fine...

Edited March 1, 2007 by rootbear75

[Incomplete]

Works fine for me, if i still had my 256 RAM stick then I might notice it but i have 2 x 1GB sticks now. Edited March 1, 2007 by Incomplete

[Dav]

My system is problem free as well

[JoWie]

Any particular page, type of content (flash,javascript) where it is occurring.

 

Tried looking in about:cache ?

[»1587200]

Every page I visit, and I cleared my cache.

[JoWie]

Does it happen when starting firefox in safe mode? (not windows safe mode) "firefox.exe -safe-mode"

Tried creating a new profile? "firefox.exe -profilemanager"

Tried reinstalling, as in uninstall first?

Using programs like windowsblinds for visual styles?

 

Try setting the following options in about:config

Some of them wont make a difference, just test what works.

 

config.trim_on_minimize = true

On Windows operating systems, when a program is minimized and left for a period of time, Windows will reclaim the memory the program used in anticipation that other programs might need it. Because of the way Mozilla applications are stored in memory, Windows is much more aggressive in reclaiming the memory they use, which can cause a delay when the program is restored. This preference determines whether to allow Windows to reclaim memory from a minimized Mozilla application.

 

Browser.sessionhistory.max_total_viewers = 0

 

Pages that were recently visited are stored in memory in such a way that they don't have to be re-parsed (this is different from the cache). This improves performance when pressing Back and Forward.

 

This preference limits the maximum number of pages stored in memory.

 

As a last resort you can try setting Browser.cache.memory.enable = false

Since you cleared your cache, I do not think this will do any good

When a page is loaded, it can be cached so it doesn't need to be rerendered to be redisplayed. This preference controls whether to use memory to cache decoded images, chrome (application user interface elements), and secure (https) pages.

Edited March 1, 2007 by JoWie

[Dav]

moving this to tech support.

 

can you try a clean install of FF?

[»1587200]

Thanks Jowie, I'll give some of that a try before I go through with a re-install.

 

And dav, this isn't Continuum related.

[Synook]

Do you have a non-standard theme? Sometimes, they can be a problem on machines with bad graphics cards... I think...