Thanks for the post Mike. It seems that I have already solved my own problem. It seems that when I have my application in a production ready state (all 50 js files combined, minified and obfuscated) firefox stops using extra memory. It seems weird that just using YUI compressor would resolve this issue but I am not going to complain.
Can anyone explain how this (combining, minifying and obfuscating) helps some memory issues? Thanks, James On Dec 7, 11:29 am, Michael Geary <m...@mg.to> wrote: > Minifying your code and removing unused code are good ways to reduce your > initial memory footprint, but they won't have any effect on memory leaks. > > A memory leak is when the browser's memory use continues to increase, either > as as you interact with a page or when you reload the page or navigate to > another page. > > (I don't make the distinction between "leaks" and "pseudo-leaks" that > Olivier mentioned. I've seen that terminology in the famous IE memory leak > paper, but I find it hopelessly confusing. It's easier for me to just say > what is actually happening: "the page leaks memory as you interact with it" > or "the page leaks memory when you reload or exit from it.") > > -Mike > > On Mon, Dec 7, 2009 at 7:32 AM, Carlos De Oliveira < > > cdeolive...@grupozoom.com> wrote: > > try to use *.min *codes (minimized versions of .js), also may remove > > Jquery UI sections from *JQuery.ui.min.js*. > > > -- > > Carlos De Oliveira > > Departamento De Sistemas > > Consultor Senior > > 0426 517 73 01 > > 0212 204 69 60 > > cdeolive...@grupozoom.com > > card...@gmail.com
