tag:blogger.com,1999:blog-13777170.post115231160941526986..comments2024-03-11T02:35:50.848-05:00Comments on grand stream dreams: Firefox Memory Leak SolutionsUnknownnoreply@blogger.comBlogger5125tag:blogger.com,1999:blog-13777170.post-1154031788704457022006-07-27T15:23:00.000-05:002006-07-27T15:23:00.000-05:00found while googling. Thank you for writing down y...found while googling. Thank you for writing down your experiences!Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-13777170.post-1152746257677145492006-07-12T18:17:00.000-05:002006-07-12T18:17:00.000-05:00You're welcome PJ, thanks for stopping by.The way ...You're welcome PJ, thanks for stopping by.<BR/><BR/>The way I read the Mozilla link posted on that entry (and I'm open to more learned readers' correction on this...)<BR/><BR/>If the browser.cache.memory.enable (b.c.m.enable) preference is set to "true" then:<BR/> a) if the browser.cache.memory.capacity (b.c.m.capacity) = "-1" the program will automatically set the "memory cache value" according to the little chart on that page.<BR/> b) if set to "0" then decoded images and chrome does not get cached in memory.<BR/> c) if any positive value (in KB) is entered, it uses that as the maximum memory cache limit.<BR/><BR/>Looking at the table, it appears the developers/programmers have somehow come up with some kind of "optimized" ratio of cached memory for Firefox (FF) to system memory. It makes sense because you probably wouldn't want FF to gobble up as much memory as it wanted, it might take it all. I'm not sure how they figured that "optimized" ratio out.<BR/><BR/>What that table actually works out to is <BR/><BR/>System RAM <--> Max FF mem. cache RAM (MB)<BR/>32 MB <--> 2 MB<BR/>64 MB <--> 4 MB<BR/>128 MB <--> 8 MB<BR/>256 MB <--> 14 MB<BR/>512 MB <--> 22 MB<BR/>1 GB <--> 32 MB<BR/>2 GB <--> 44 MB<BR/>4 GB <--> 58 MB<BR/><BR/>My "default" value found in that field was 65536 which would be equivalent to 64 MB RAM (maximum). <BR/><BR/>So the way I am understanding it, my "default" about:config load had the b.c.m.enable key set to "true" and the b.c.m.capacity = 65536 (not the -1 like it should be). Therefore FF was allowed to use up to 64 MB of my RAM for memory caching. YIKES! Again, IF I am understanding this correctly, then FF would keep creeping up in the memory usage until it hit that 64 MB limit. I don't like that idea since I only have 512MB system RAM on this pc.<BR/><BR/>By setting my b.c.m.capacity (according to the table) to the 22528 value, I'm forcing it to only creep up to 22 MB RAM for this particular type of caching activity. I could actually have set it lower, but it seems like a good balance for my personal system's needs. I should have also just been able to type in "-1" and achieve the same result. But I can relate to 22528, not as well with "-1".<BR/><BR/>Did that make sense?Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-13777170.post-1152725435626063332006-07-12T12:30:00.000-05:002006-07-12T12:30:00.000-05:00Thanks for all the tips. Did not understand how yo...Thanks for all the tips. Did not understand how you got to 22528 to match 512 MB physical RAM in browser.cache.memory.capacity.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-13777170.post-1152367269785137152006-07-08T09:01:00.000-05:002006-07-08T09:01:00.000-05:00I notice that in my post I forgot to mention the v...I notice that in my post I forgot to mention the version of Firefox I am using. <BR/><BR/>It is Firefox 1.5.0.4.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-13777170.post-1152331011915905212006-07-07T22:56:00.000-05:002006-07-07T22:56:00.000-05:00I'll give this a try to see if it works on Mozilla...I'll give this a try to see if it works on Mozilla.Anonymousnoreply@blogger.com