Evidence is coming in in the browser memory wars: Winner – Firefox 3.
There are several points of comparison between browser’s memory consumption. First, total memory used. The clear winner here is Firefox 3, with Safari (though it is a Mac product, there is a Windows version) as a strong looser. That’s “strong” as in “way off by itself”.
Second, how memory is used. And this leads to the reason Firefox 3 is such a clear winner and Safari is so poor. In our C++ class, indeed, discussed in the Java class – and those are “class” as in “education, school, that room you sit in with others to be awed by the teacher” – is memory usage and cleaning up after yourself. Java does that automatically while C++ requires some work on the programmer’s part to keep the stack purged of no-longer needed memory locations. It seems that those bright people at Firefox, after having gotten dinged so badly with Firefox 2, listened to that particular part of the lecture while for the Safari folks the lecture was given on the Monday after the kegger party thrown to celebrate the school’s winning the opening game against their bitterest rival. In other words, Firefox opens with an initial amount of memory and then usage graphing goes flat, while Safari just keeps opening more and more memory with each site or page opened. Folks, if I ain’t viewing the page there is really no reason to keep that page’s memory hanging around as if it is still in use!
For more details, and links to the original article, check out this Computerworld article.