Quote:

main problem with firefox is that is has a massive memory leak and can consume over 100mb of memory. Right now i'm at 87mb. I don't know why they don't fix it.


My FF task is generally about 400 MB. I haven't had a problem with memory leaks in any version of FF.

"Leak" has a technical term for programmers that means that repeating at least one action (clicking on a link over and over for example) would cause resource (memory) to be (unexpectedly) unavailable in the future. In other words, being 87 MB is not a leak, but increasing 100 KB in size with each downloaded file would be.

The statement "Firefox is supposed to dynamically release memory from its RAM cache to other Windows applications as needed" is wrong when applied to the FF cache; that guy doesn't understand paging! But limiting the cache might work if there is a design problem in the FF cache or the Windows VM system. It's credible since the NT VM has some weird paging algorithms I don't think have ever been documented - probably more 1970's-era VMS thinking - and nobody really knows how to tune a large in-process cache for Windows.
_________________________
"If they can't picture me with a knife, forcing them to strip in an alley, I don't want any part of it. It's humiliating." - windsock