Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!

 



Forgot your password?
typodupeerror

Slashdot videos: Now with more Slashdot!

  • View

  • Discuss

  • Share

We've improved Slashdot's video section; now you can view our video interviews, product close-ups and site visits with all the usual Slashdot options to comment, share, etc. No more walled garden! It's a work in progress -- we hope you'll check it out (Learn more about the recent updates).

×

Comment: Re:how long (Score 1) 152

by Kinematics (#41634929) Attached to: Mozilla Details How Old Plugins Will Be Blocked In Firefox 17

The amount of memory Firefox uses has always been a catch-all statement for bad behavior and poor performance, not a strict indication of the problem of running out of RAM (usually).

Personally, for a very long time, if Firefox crossed 1 GB of RAM usage, I could pretty much guarantee issues with slow tab switching, glitchy scrolling, the browser as a whole briefly hanging every few minutes, sometimes even bogging down my entire OS if it decided to saturate the CPU.

The degree to which this effect manifested could pretty much be exactly tied to its current RAM usage. I started to notice it at 700 MB, it was annoying at 900 MB, and at 1.1 GB it was completely unusable. This had absolutely no correlation with the total amount of RAM in the system. If I have 2 GB or 32 GB, it doesn't matter. Once Firefox crossed 1 GB, it was all over.

So when people say, "It uses less RAM", I hear, "It's less likely to reach a state that I have noticed invariably leads to poor performance all around", not "I just saved $300 on my car insurance"... er, "I just saved 300 MB of my overall RAM pool that I can use for other stuff".

If a thing's worth having, it's worth cheating for. -- W.C. Fields

Working...