Thanks a bunch for that link, also Josh for your advice. After running this leak detector, nothing found as well.
Also, the 300MB leak hasn't recurred since that one time. My current best guess is that the leaks occurred while I was debugging javascript code and refreshing the page -- so the leaks were probably due to bad code since fixed. But since it was the same browser session refreshed again and again, leaked DOM memory wasn't reclaimed until I closed and re-opened the browser. Anyway, I'll keep an eye on it, but I've got some good tools to help, and jQuery is itself excellent at GC anyway so I hopefully won't run into a problem. Thanks again, JK -----Original Message----- From: jquery-en@googlegroups.com [mailto:[EMAIL PROTECTED] On Behalf Of trixta Sent: Wednesday, November 05, 2008 6:15 AM To: jQuery (English) Subject: [jQuery] Re: Advice on sIEve/Drip? On Nov 4, 12:20 am, "Jeffrey Kretz" <[EMAIL PROTECTED]> wrote: > OUCH. > > With over 25,000 lines of javascript code (full featured CMS) that's a > nightmare to track down. > > Am I out of luck? Are there no other alternative tools like sIEve that are > still in development? > Hi, there is another tool by microsoft, you can try: http://blogs.msdn.com/gpde/pages/javascript-memory-leak-detector.aspx but this tool doesn´t find all memory leaks. this jquery-related info could be helpfull, too: http://groups.google.com/group/jquery-dev/browse_thread/thread/4a99f6e9b2e33 057/30099a04db7f87b9 http://www.outsidethediv.com/2008/10/removechild-vs-the-garbage-bin/ One last advice. You don´t have to fix all memory leaks in IE6. It really depends on the cost-benefit-ratio (hard effort/work to fix it vs. noticeable advancement for the enduser). regards alex
