DVD Talk
Firefox a huge memory hog? [Archive] - DVD Talk Forum
 
Best Sellers
1.
2.
3.
4.
5.
6.
7.
8.
The Longest Day
Buy: $54.99 $24.99
9.
10.
DVD Blowouts
1.
2.
3.
4.
5.
6.
7.
Alien [Blu-ray]
Buy: $19.99 $9.99
8.
9.
10.

PDA
DVD Reviews

View Full Version : Firefox a huge memory hog?


mikehunt
02-09-05, 02:17 AM
I've noticed this a few times before. with just 2 pages(in tabs not separate windows) open, dvdtalk and a similar forum site, FF was using 60megs of memory. closed and reopened it and right now it's sucking up 45megs with 4 pages(again, in tabs) open
is this normal? It's FF 1.0 but I've noticed it with 0.9.3 too

wmansir
02-09-05, 02:29 AM
I would say so. I have 4 pages open, this one and 3 google results, and it's using 139MB ram 149MB VM. It's been up for a while though, let me see what it is if I close and reopen it...


Now with just this page its 39MB RAM 28MB VM.

BigPete
02-09-05, 09:02 AM
According to the folks on Slashdot, it does have a few bad memory leaks.

Jeremy517
02-09-05, 10:29 AM
It is due to the way it caches things. It supposedly will never use more than you reasonably can afford to have being used.

If you want to clear the cache, just minimize the app. That drops usage for me down 1.5 MB or so.

PixyJunket
02-09-05, 12:43 PM
Among other things.. but yes.

madara
02-09-05, 12:47 PM
It always loads pictures really slowed compared to IE but its ability to avoid pop-ups and scams way over rides that for me.

namja
02-09-05, 01:24 PM
Right now, I have six IE windows open and six FF windows (not tabs) open:

http://www.coldpumpkin.com/upload/task.jpg

IE is using up a little more memory than FF.

Tsar Chasm
02-09-05, 01:32 PM
It always loads pictures really slowed compared to IE but its ability to avoid pop-ups and scams way over rides that for me.

I can't remember where I got this but...

* Run Firefox? Have broadband? Here's Speed Tips

Here's something for broadband people that will really speed up

Firefox:

1.Type "about:config" into the address bar and hit return.

Scroll down and look for the following entries:

network.http.pipelining

network.http.proxy.pipelining

network.http.pipelining.maxrequests

Normally the browser will make one request to a web page at a time. When you enable pipelining it will make several at once, which really speeds up page loading.

2. Alter the entries as follows:

Set "network.http.pipelining" to "true"

Set "network.http.proxy.pipelining" to "true"

Set "network.http.pipelining.maxrequests" to some number like 30.

This means it will make 30 requests at once.

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 receives. If you're using a broadband connection you'll load pages MUCH faster now!

pdutta2000
02-09-05, 01:41 PM
Right now, I have Firefox open with 18 tabs and it's taking 48 megs. One of my IE windows is open with Outlook Web Access and it's taking 35 megs. I have seen Firefox go up to 90 megs at some points.

Breakfast with Girls
02-09-05, 01:59 PM
It always loads pictures really slowed compared to IE but its ability to avoid pop-ups and scams way over rides that for me.It's been my experience that Firefox handles JavaScript and complex HTML a hell of a lot faster than Explorer, though.

As far as memory, Firefox and Explorer are about the same. The difference is that since Explorer is an SDI application, the memory is split up per window, whereas Firefox has everything under one process (even if you don't use tabs). I doubt it would use more memory than is free.

There was a memory leak, but I believe it was fixed.