Mozilla To Tackle Firefox Memory Leaks
As FavBrowser recently reported, there are ways to get around memory leaks in Firefox. Nevertheless, the problem appears to be serious enough for Mozilla itself to finally want to get it out of the way.
It’s become increasingly clear over the last several months that we have a pretty pressing need to deal with increases in memory usage in Firefox. Since we released Firefox 4 (and before, too), we’ve seen lots of reports about Firefox memory usage being higher than in older versions, and that Firefox memory usage is growing over time. – Johnny Stenback, a developer who works for Mozilla.
In response to the issue at hand, an initiative titled MemShrink by Mozilla has been launched in the hope of concluding Firefox’s memory leaks.
MemShrink includes Mozilla holding weekly meetings for developers to triage bugs, produce plans to fix bugs, and assign them to specific programmers.
It’s pretty clear by now that this is a much bigger problem than any one person can likely tackle. – Stenback.
More details on MemShrink can be found here. This is what many of you have been waiting for, no?
About (Author Profile)
Being passionate about software, Armin joined FavBrowser.com in early 2011 and has been actively writing ever since. Having accepted the challenge, he also enjoys watching anime, indulging in good books, staying fit and healthy, and trying new things.
Subscribe
If you enjoyed this article, subscribe to receive more just like it.
Mozilla have been promising to fix the memory for years and never did. Whats changed?
Actually, I remember Mozilla denying there were any memory leaks initially. But when Firefox 3.0 was launched, their most trumpeted feature was that they had fixed a lot of memory leaks. So they fixed something that didn’t exist :) .
Actually, I remember Mozilla denying there were any memory leaks initially. But when Firefox 3.0 was launched, their most trumpeted feature was that they had fixed a lot of memory leaks. So they fixed something that didn’t exist :) .
Actually, I remember Mozilla denying there were any memory leaks initially. But when Firefox 3.0 was launched, their most trumpeted feature was that they had fixed a lot of memory leaks. So they fixed something that didn’t exist :) .
Actually, I remember Mozilla denying there were any memory leaks initially. But when Firefox 3.0 was launched, their most trumpeted feature was that they had fixed a lot of memory leaks. So they fixed something that didn’t exist :) .
It’s unfortunate is these times, all it needs is to APPEAR TO DO the right thing, you no longer have to actually DO the right thing.
Mozilla and Microsoft (the worst offenders of this type of PR, unsurprisingly, both American) are famous for this, and have spin departments whose sole purpose is to manage this type of PR (the FUD/Spin/Astroturding dept.)
A lot of browsers have Memory leak if you
keep using it enough long as far as I know, such as the browsers based on IE, like
maxthon avant browser. I don’t think they have a method to solve the problem
completely. Of course, it ‘s a good thing once they success
makes me nervous