Nspr_leaks.log – the file where you can see if you had any leaks during the session. Then, after you’ve closed Firefox, you can see 2 files: Just put it in the Firefox directory, put in C:\mozilla\ and then run it. I’ve made a batch file that does all the things automatically Install Perl in windows to track memory leaks? Uh. Oh, and if you want leaks, go to with JavaScript turned on, (and for best effect, open up lots of tabs at once on that site). It would be nice if any leak fixes which are trivial/have a large impact could be considered for inclusion into the Firefox 1.5.0.* updates and also the 1.8.1 branch. So is dbaron going to (try to) fix all the memory leaks I would find? ) Sirve tanto para Windows como para Linux (aguante perl). Jesse Ruderman de Mozilla tiene un post de una herramienta para detectar los famosos memory leaks (alguien traduzca eso a algo que no de asco) en Firefox. Herramienta para detectar problemas de memoria en Firefoz… Sometimes Firefox’ performance slows down to a crawl. I regularly restart Firefox to free memory, after it has allocated up to 300MB of RAM (not sure if this includes virtual memory) due to heavy tab usage (open new tab from feed reader, read page, close tab). I’m glad to see that David works so hard on reducing Geckos memory footprint. You can follow any responses to this entry through the RSS 2.0 feed.īoth comments and pings are currently closed.ģ2 Responses to “Firefox memory leak detection tool” On Friday, January 13th, 2006 at 4:31 am and is filed under Mozilla, Performance. Bug 323075, which lists David Baron's ideas for an extension that would monitor JavaScript memory use.Bug 320192, where was introduced and where the associated patches lived.David Baron: Using XPCOM in JavaScript without leaking.David Baron: How to file useful leak bugs.Update : There's also a JavaScript version, which might be easier to use if you use Windows and don't have Perl. contains instructions for making Firefox log the required information and for running to analyze the log. If you're using Windows, you'll also need to download Perl. To use, you need a version of Firefox with the logging code, such as a recent trunk nightly build.
David Baron has already fixed one of them on the trunk. I have found three leaks so far with this tool. It tries to report the URLs associated with the leaks it detects, allowing you to go back and figure out the steps needed to reproduce the bug. It detects many large leaks even though it only tracks three types of objects (documents, docshells, and domwindows) because many large leaks entrain at least one of those objects. With this tool, you can find out what leaks you encounter during your normal browsing patterns and report useful bugs when you encounter leaks. David Baron recently wrote a tool that testers can use to help reduce memory leaks in Firefox.
0 kommentar(er)
