I just want to point out that we'll never "fix all the memory leaks", and we should never claim otherwise. Firefox has millions of lines of code, and we're constantly changing it. As hard as we try, we occasionally introduce new leaks (e.g. [1]). And as we change the browser, the amount of memory it uses also changes -- this can give the appearance of "leaks" when there are none per se.
The right question to ask isn't "are the leaks finally fixed?" but "how has the chance that Firefox's memory usage is acceptable for my workloads changed over time?" In this respect, we've made demonstrable progress, as we've not only decreased memory usage for average workloads (as indicated by the telemetry we collect from users who opt in [2] and by our automated tests [3]), but we've fixed a number of edge cases which were causing some users to see high memory usage. (For example, we fixed the vast majority of leaks caused by add-ons.)
jlebar51 karma
I just want to point out that we'll never "fix all the memory leaks", and we should never claim otherwise. Firefox has millions of lines of code, and we're constantly changing it. As hard as we try, we occasionally introduce new leaks (e.g. [1]). And as we change the browser, the amount of memory it uses also changes -- this can give the appearance of "leaks" when there are none per se.
The right question to ask isn't "are the leaks finally fixed?" but "how has the chance that Firefox's memory usage is acceptable for my workloads changed over time?" In this respect, we've made demonstrable progress, as we've not only decreased memory usage for average workloads (as indicated by the telemetry we collect from users who opt in [2] and by our automated tests [3]), but we've fixed a number of edge cases which were causing some users to see high memory usage. (For example, we fixed the vast majority of leaks caused by add-ons.)
[1] https://bugzilla.mozilla.org/show_bug.cgi?id=795221 [2] http://bit.ly/memorytelemetry [3] https://areweslimyet.com/
View HistoryShare Link