Padd Solutions

Converted by Falcon Hive


The earlier post about my shifting browser preferences and RAM-hoarding contained a few anecdotal claims about Firefox and Safari, but little in the evidence department. By way of showing you some, let me link to you Lifehacker's recent conversation with Mike Beltzner, the director of Firefox. The whole thing is quite interesting for a net-denizen ignorant of the nuts-and-bolts of browser design, and Beltzner provides some interesting insight into what sorts of things contribute to a browser's hold on your system's memory. Money quote:

Feedback about memory usage is definitely something we hear frequently from our users, and without wishing to blamecast, most frequently the issue is actually related to poorly coded plug-ins, add-ons, and web pages. We did a great deal of work for the Firefox 3 release to make our memory allocation more efficient, as well as create technology that cleans up after some of the common problems created by plug-ins, add-ons, and web pages, but the truth of the matter is that a lot of webpages create plug-in-rendered elements that leak memory over time. The longer you hold that page open in a tab, the more memory will leak out.

(0) Comments