I had 67 firefox windows open this morning (seriously), and it was only using 375 megs of ram. What a hog.
This is how you fix this "memory leak" problem when FF bogs down. (It's not actually a leak, it just doesn't flush the cache it has.)
1)Type about:config into the location bar and press enter
2)Right click any line to bring up a sub-menu
3)Choose "new">"integer"
4)paste this into the dialogue that appears: browser.cache.memory.capacity
5)Next click Okay
6)Specify the amount in kb (about 60000 should do) in the next dialogue that appears
7)Restart Firefox and happy surfing.
its pretty unstable for me it crashes just like IE used to,
if I let it run for a day or two it eats all my cpu
and some other bugs. I notice this only on windows tho, on *nix seems to
run better.
I rebooted, deleted temp files, history, cookies and everything...still cannot view the news clip. All I see is that fucking gay ass music video from "Rick Roll". Anyone else have a different link to the news clip?
Has anyone else noticed any sites that won't load when you are using adblock? They used to load for me no problem, but now key bits are left off. I wonder if that is the site fighting back against the loss of ad rev....
maybe you bitches should learn how to use a web browser first instead of constantly blaming the software!! i've used IE since 1997 and I've never had any problems!! haha!
i had some issues recently with 1.0.6, eating to much memory
but after updating to 1.0.7, it somehow fixed the problem.
its just a matter of time before Mozila releases the final and
stable new version, 1.5 can't wait
I just wish they'd dump XUL. It makes applications slow and ugly. K-Meleon uses the same rendering engine as Mozilla Firefox (Gecko) but uses the native Win32 interface, hence runs way faster and stable than Firefox. Too bad you can't use Extensions and it's development is extremely slow.
K-Meleon uses the same rendering engine as Mozilla Firefox (Gecko) but uses the native Win32 interface, hence runs way faster and stable than Firefox. Too bad you can't use Extensions and it's development is extremely slow.
This is how you fix this "memory leak" problem when FF bogs down. (It's not actually a leak, it just doesn't flush the cache it has.)
1)Type about:config into the location bar and press enter
2)Right click any line to bring up a sub-menu
3)Choose "new">"integer"
4)paste this into the dialogue that appears: browser.cache.memory.capacity
5)Next click Okay
6)Specify the amount in kb (about 60000 should do) in the next dialogue that appears
7)Restart Firefox and happy surfing.
That info is wrong. It should by 16000 not 60000. Otherwise it's still gonna leak memory. They should've had this problem fixed by now. I think it is supposed to be fix in the final 1.5 release. *shrug*
Fling.com doesn't steal your traffic and sales unlike some other dating companies. I promote them, and so should you!
Comment