Having done a fair amount of memory debugging I can tell you that you have little choice (in JavaScript/Browser land) but to eliminate functionality and watch the memory footprint. It's a good argument for writing unit tests that you can run 1000 times to see what happens. FWIW, in my experience memory issues that persist from one page load to the next are pretty rare in Firefox w/ MooTools. Memory growth in a static page that is constantly loading in new content via ajax and the like is much more likely. Look for plugins that create things without destroying them, esp. if you are creating a lot of them.
For windows, I recommend process explorer to watch the memory of a specific instance: http://technet.microsoft.com/en-us/sysinternals/bb896653 This old article of mine on the topic might be of interest: http://www.clientcide.com/best-practices/browser-issues/screencast-on-diagnosing-memory-leaks-in-ie/ On Wed, Jul 13, 2011 at 8:10 AM, Trevor Orr <[email protected]> wrote: > I am running into the the same thing with Firefox 5, I personally think it > is Firefox and not your app, I have so many issues with this latest version > of Firefox I think am going to go back to version 3.6 > > > > > On Wed, Jul 13, 2011 at 7:48 AM, Martin Hewitt <[email protected]>wrote: > >> Hi all, >> >> Just wondering if anyone had any hints, tips or best practices as to how I >> might go about diagnosing a memory leak in a Mootools-powered web app >> running in Firefox. >> >> Testing it locally, refreshing every couple of minutes, firefox's memory >> footprint balloons to the point where it's paging to disk continually and I >> eventually have to restart. >> >> Any help would be greatly appreciated. >> >> I'm using MooTools 1.3 and Firefox 5 on a Mac. >> >> Martin >> >> >
