Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Progress is nice, but unfortunately as a user I don't care too much about progress if the bottom line is the same. Sorry to sound disdainful about your efforts, and I know how hard it is, and I have greatest respect for the efforts of Firefox developers, but the bottom line is - it is (was, last time I checked) still leaking like Eratosthenes' sieve, and still becomes unusable after mere days of work. And even admiration for the product and all the history of it can only hold the user for so long when viable alternative is out there.


To counter your anecdote with another, different anecdote with more numbers in it, back in the days of Firefox 4 and subsequent versions, it would not be unusual for my Firefox to hit 500MB to 1GB of RAM usage after a day of browsing. Right now, my Firefox 15 has been running for a day, and about:memory says the total is 363.26MB. Firefox has slimmed down a lot in the past year.


Well, maybe I'll give it a try soon again. I did about a year ago and was re-disappointed.


The first big post-FF4 improvements were in FF7, which was released in September last year. See http://blog.mozilla.org/nnethercote/2011/08/09/firefox-7-is-... for some details.

And things have improved quite a bit more since FF7.


I personally noticed this too.


> still leaking like Eratosthenes' sieve

It leaks a lot when it's using a tiny amount of memory, and it leaks hardly at all when it's using a large amount of memory?


No, it leaks endlessly without any theoretical bounds and there's no amount of memory that it's leaking won't exceed given enough time.


So you're saying that it's more like a normal sieve than Eratosthenes' sieve?


Apparently it only leaks into address locations that are prime, and setting all others to null.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: