Tuesday, November 13th 2007
Mozilla Still Perplexed as to Why Firefox Takes So Much RAM
Anyone who uses Mozilla Firefox in a Windows environment knows that Firefox can use a lot of memory. Now that Mozilla is getting a lot of requests to make a mobile version, they are working very hard to make a version that won't eat all of the mobile phone's memory. Christopher Blizzard, a member of Mozilla's development board, had this to say about Firefox's alleged memory issues.
Source:
CRN
As Mozilla starts down the path to running in the mobile space we are spending time looking at memory pressure issues more closely. . . (I)t sounds like the early data suggests that Mozilla really doesn't leak that much memory at all. But it does thrash the allocator pretty hard and that's what causes the perception of memory leaks.
56 Comments on Mozilla Still Perplexed as to Why Firefox Takes So Much RAM
But with at least 2gb of ram in my PC(s), I don't give a sh*t about 50-200mb of ram used by FF.
A memory leak is a pool of resources that will never be released, or have control transfered back to the kernel of the OS.
For example, after awhile of playing one of the CIV games, a older one, under Windows 98 and after quitting the application memory that should have been free for other applications was marked as in use, due to files and cache still being loaded.
But Cache that is still in use, such as recently visited webpages or downloads is not a memory leak, it is just bad programming, or a bad interface between what the program marks as active set and what the OS keeps in page for physical RAM.