jason longboard;2427694; said:
Troll? mmkay. Anyways Firefox uses up too much memory especially when you have 4-5 tabs open.
firefox
- Thread starter jason longboard
- Start date
Troll? mmkay. Anyways Firefox uses up too much memory especially when you have 4-5 tabs open.
meaning that if you got mfk,and another something going then when you try to open something else it goes too slow?evilxyardxgnome;2428472; said:
jason longboard;2428790; said:
Meaning, my pile of crap lap top can't handle so many tabs open in FireFox, but with IE I don't have the memory leak problem. FireFox has always had a memory leak problem Mozilla knows this and FF 3 was supposed to solve this issue, but it hasn't been solved.
Miguel;2426768; said:
Yes, during the set-up process it will ask you if you would like to import settings and other data from IE. Also, sometimes I run several tabs. I have a 6 year old entry-level Dell desktop with minimal issues mostly. Especially after loading up with add-ons like ABP, NoScript, and WOT. I've found that firefox runs faster than IE. You can also adjust the settings to run a little quicker. It'll warn you about changing the setting but if you follow these directions exactly [it's pretty easy] you should increase the browsing speed a bit. 1. Type about:config into the address bar and hit return. 2. Alter the entries as follows (by double clicking each entry): Set network.http.max-connections to 48 Set network.http.max-connections-per-server to 24 Set network.http.max-persistent-connections-per-proxy to 12 Set network.http.max-persistent-connections-per-server to 6 Set network.http.pipelining to true Set network.http.proxy.pipelining to true Set network.http.pipelining.maxrequests to 8. Any more and you may get banned from the site visited, as it may be viewed as DOS attack. Try a higher value say upto 32 but be prepared to lower the value if sites fail to load. 3. Lastly right-click anywhere and select New-> Integer. Name it nglayout.initialpaint.delay and set its value to 0. This value is the amount of time the browser waits before it acts on information it recieves.
