BillLeeLee
[H]F Junkie
- Joined
- Jul 2, 2003
- Messages
- 13,486
over 1.2 GB used. ...Impressive, huh? They really gotta implement a fix for the whole images thing.
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
Oh it's nothing i just had FF grain out like that on me today earlier and I was wondering if it was happening again.BillLeeLee said:Sorry, it's a result of me making it a GIF in MSPaint.
Kaiga said:wow, thats terrible, like what is firefox running there? I bet you have like 20 tabs open and downloading a bunch of crap at the same time through it.
and yes, thats also terrible, your window shot is grainy. wtf?
BillLeeLee said:They really gotta implement a fix for the whole images thing.
Shadow2531 said:I'm now using this build of Firefox from http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/2005-12-21-06-trunk/
(latest trunk for today)
It's working nicely and has been stable, so far.
You might want to *test* it out to see if your problem is fixed with this build.
Qwertyman said:this is much faster than 1.5 its ridicilous.
Terpfen said:The "Firefox leaks memory like crazy look at this!" posts are starting to grate a little.
Folks, there is a very simple solution to this. Go to about:config, right-click, create a new boolean value, type config.trim_on_minimize in the first window, and select true in the second.
Now Firefox will release nearly every MB of RAM it uses when you minimize it. After bringing Firefox back into focus, it will only use the bare minimum of RAM it needs at that time. What happens after FF starts sucking up another 200MB of RAM? Minimize again. It's like magic, except not!
Shadow2531 said:Opera does this automatically. We've been told that this is a standard windows feature.
However, we've been told that it doesn't really free memory. It just dumps it to the page file and when the browser needs it back, there's a performance hit because it's grabbing things from disk instead of memory.
One clarification: this patch does _not_ prevent Mozilla from releasing memory
for other apps (that is, being swapped out). It's just that it won't happen
before it's necessary, and only the needed amount of memory is "moved" from
Mozilla to the other program. This is the same thing that happens if you leave
Mozilla to the background and start another program.
mosin said:Without the tweak config.trim_on_minimize...
Shadow2531 said:A few sources on the subject:
Shadow2531 said:I'm now using this build of Firefox from http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/2005-12-21-06-trunk/
(latest trunk for today)
It's working nicely and has been stable, so far.
You might want to *test* it out to see if your problem is fixed with this build.
Shadow2531 said:Crap.
Nevermind on the build. I found a sore spot. Image maps with application/xhtml+xml are broken. Oh well, to be expected.
ImStillDave said:I gave up on Firefox for the time being... I'm using Opera and loving it
Then you haven't been using version 1.5sculelos said:I dunno I never had a problem with firefox, so I dunno.