[FireFox] Had to share this


Recommended Posts

Yea, Firefox has become a real resource hog. Even with 1GB of Ram, it still tends to slow down browsing for me. I'll load 1 tab, click 2 links to open in new tabs and load in the background, and Firefox will just freeze while at least the first one finishes loading. :dontgetit:

Link to comment
Share on other sites

More of Mozilla's overrated coding at work. They never were very good at the basics.

*ouch* :pinch:

But I tend to agree with you there.

For the time being I think I'll go back to IE sometimes I use Opera now too since I miss tabs.

Link to comment
Share on other sites

If you are using Firefox 1.5 it is because of the new Fast-back browsing. Everything is kept in cache so that if you hit back button everything is loaded instantly and does not have to be re downloaded.

If you want to disable this change this in about:config 'browser.sessionhistory.max_viewers' to 0, if at 5 that will saved everything that was loaded in last 5 pages in that tab. SO if you have a few tabs open that could be 25 tabs worth of pictures causing all that ram useage.

Thank's , thats useful :)

Link to comment
Share on other sites

I still have Firefox 1.0.7... I haven't upgraded yet because of all this negative stuff I'm hearing about 1.5. I find that my version of FF uses far too much memory as well. I always have about 4 tabs open though - so that might be the problem.

Also, when we say FF uses too much memory, what are we saying is the average amount of memory we're expecting FF to use? (if that makes any sense).

Link to comment
Share on other sites

1.5 has no problems. If you want to avoid problems, dont upgrade, wipe your current installation (might wana backup your profile if your REALY worried), then do a fresh install and install all the extensions again. Overkill IMO but I did it that way anyways.

FF memory leakage has been a long history, it's supposed to be fixed in 2.0

AND, it does use extreamly large ammounts of memory as a browser. It's very true.

Link to comment
Share on other sites

They have this shiny new auto-update feature so you're saying they're gonna sit around till 2.0 to fix this? It seemed to take forever for them to get 1.5 out the door.

nono i never said anything. according to sources (sources consisting of about 100% of the web population, with +/- 1% margin of error) it's going to be released in 2.0 because 1) it's such a huge bug that they couldent fix it in 1.5, so they are fixing it in the next release, and 2) the next release IS 2.0.

What does that have anything to do with the new autoupdate feature?

Link to comment
Share on other sites

FF memory leakage has been a long history, it's supposed to be fixed in 2.0

As an (ex)long-time Mozilla software user I can tell you, they've said they're going to be fixing their memory leak issues in "their next release" since about Netscape 6 PR-1 (in 2000). It's not going to happen.

And for those know don't know what Netscape PR-1 is, here's a screnshot:

post-27111-1134445884.jpg

Link to comment
Share on other sites

nono i never said anything. according to sources (sources consisting of about 100% of the web population, with +/- 1% margin of error) it's going to be released in 2.0 because 1) it's such a huge bug that they couldent fix it in 1.5, so they are fixing it in the next release, and 2) the next release IS 2.0.

What does that have anything to do with the new autoupdate feature?

I was implying that they could patch the leaks and use the auto-update instead of waiting and releasing an entirely new exe/version for everyone to download like we used to have to do. Was under the impression thats what auto update was meant for.

Link to comment
Share on other sites

I was implying that they could patch the leaks and use the auto-update instead of waiting and releasing an entirely new exe/version for everyone to download like we used to have to do. Was under the impression thats what auto update was meant for.

yea they could if they had an update for it.

Link to comment
Share on other sites

I know as of now they have no remedy, but it seems they're taking the stance of security updates only from auto-update and actual browser fixes (like this issue) are being saved for version upgrades.

Link to comment
Share on other sites

What version are you running?

I'm running 1.5 and have about 8 tabs open right now. Only using about 60k.

post-40930-1134270865.jpg

I'm pretty sure bangbang answer is right, since he works on those nightly builds.

/EZ

It is not 60K. It is 60 MB

Link to comment
Share on other sites

As an (ex)long-time Mozilla software user I can tell you, they've said they're going to be fixing their memory leak issues in "their next release" since about Netscape 6 PR-1 (in 2000). It's not going to happen.

And for those know don't know what Netscape PR-1 is, here's a screnshot:

:rofl: Maybe Firefox 3.0 then...

Link to comment
Share on other sites

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.