Next Generation Emulation banner
1 - 13 of 13 Posts

·
Elven-Dragon Mage
Joined
·
2,828 Posts
Discussion Starter · #1 ·
firefox constantly uses upwards of 300,000K on my memory usage in windows xp even when all im doing is post this here thread. ill post what extension and plugins ive got if needed. and my flash videos all lag a bit as well. ive got the latest version of flash version 10 not 10.1 becuase my gpu cant handle the loadoff becuase its only a 7600 and it looks like they use cuda for the load off.
 

·
Banned
Joined
·
23,263 Posts
Thats normal for a firefox that is using default settings for Fastback cache.

CUDA is not used, DXVA2 is used. and while a 7600 cannot do h264 acceleration it can accelerate other formats.
 

·
Elven-Dragon Mage
Joined
·
2,828 Posts
Discussion Starter · #3 ·
not normal for eveything to lag tho huh? and i didnt see this high of mem usage on windows 7 and i sure didnt get the freezes im getting. talking bout firefox freezing completely that i have to terminate the proccess. im using the latest non beta version of firefox
 

·
Banned
Joined
·
23,263 Posts
Go back to 3.5.2 alot of people are getting freezes with 3.5.5, or install 3.7alpha which has recently (finally) had a patch landed that fixes the session crashes i was getting.

its as stable as 3.5.2 is, without the long startup times, and with better CPU usage overall.
 

·
Elven-Dragon Mage
Joined
·
2,828 Posts
Discussion Starter · #5 ·
ill try it and see what happens hope the latest alpha version helps. wow i see a lot of my extensions aren't compatible with the latest version which sucks
 

·
Registered Anime Hater
Joined
·
8,674 Posts
It's an alpha version, what did you expect? :p

Anyway, before anything run FF is safe mode (which disables all the add-ons) and see what memory usage is like with that.
 

·
Banned
Joined
·
23,263 Posts
install Nightly Tester Tools, this forces the addons to work.

most, if not all addons compatible with 3.5 will work on 3.7.
 

·
Banned
Joined
·
23,263 Posts
i've not verified that 3.6 has the crash fixed.

but other then that, 3.7 has a better js core, html5 and webgl
 

·
┐( ̄ー ̄)┌
Joined
·
2,058 Posts
Strange that the new beta 3 has almost same changelog as you mentioned
* (NEW) Changes to how we allow third party software to integrate with Firefox in order to prevent crashes.
* (NEW) The ability to run scripts asynchronously to speed up page load times.
* More than 80 bug fixes from the last beta to improve performance, stability, security and features.
* This beta is available in more than 60 languages - get your local version.
* Users can now change their browser's appearance with a single click, with built in support for Personas.
* Firefox 3.6 will alert users about out of date plugins to keep them safe.
* Open, native video can now be displayed full screen, and supports poster frames.
* Support for the WOFF font format.
* Improved JavaScript performance, overall browser responsiveness and startup time.
* Support for new CSS, DOM and HTML5 web technologies.
I suspected they're same :heh:
 

·
Registered
Joined
·
603 Posts
Go back to 3.5.2 alot of people are getting freezes with 3.5.5, or install 3.7alpha which has recently (finally) had a patch landed that fixes the session crashes i was getting.

its as stable as 3.5.2 is, without the long startup times, and with better CPU usage overall.
Is 3.5.5 really that bad? I've been using it for quite a while now with no problems in Windows 7. The highest usage I've seen so far is about 100,000K, but that's only after I've kept it open for over a day. So far haven't experienced crashes yet.
 

·
Banned
Joined
·
23,263 Posts
Just verified, the JsInterpret crash is still not fixed in 3.6, but is fixed in trunk.

firefox is now hanging around the 85,000K mem usage in safe mode
Then its not Firefox / Plugins that are the problem. use process explorer and check the list of dll's loaded with explorer / firefox processes.
 
1 - 13 of 13 Posts
This is an older thread, you may not receive a response, and could be reviving an old thread. Please consider creating a new thread.
Top