I found that using sIEve wasn't that much more useful than just watching IE memory usage.
Your code leaks even if you can't figure out where it is. I traced down my own leaks by running suspect functions 1,000s of times. --matt On Nov 3, 3:38 pm, "Jeffrey Kretz" <[EMAIL PROTECTED]> wrote: > I figured I'd bring this up again - I'm really hoping someone here has some > advice for me on this. > > Buehler? > > JK > > From: jquery-en@googlegroups.com [mailto:[EMAIL PROTECTED] On > Behalf Of Jeffrey Kretz > Sent: Friday, October 31, 2008 4:56 PM > To: jquery-en@googlegroups.com > Subject: [jQuery] Advice on sIEve/Drip > > While debugging my application (which makes heavy use of jQuery), after > several hours IE had consumed about 300MB. > > So I figure I've got some memory leaks. > > I tried sIEve 0.8 and wasn't able to find anything specific that was leaking > or causing problems. I tried the system, dragged things around, opened > various popups, etc. Basically used a while series of functions on the CMS. > No leaks reported at any time. > > I then pulled up one of heavier js pages and put it auto-refresh for about > 10 minutes. It slowly went from 61MB to 66MB over a 10 minute period. > > At no point during the auto-refresh, or during the other stages when I was > actually using the system, dragging things around, etc. were any specific > leaks reported. > > Are there other actions I can take to track down the problem? > > I noticed that sIEve/Drop hasn't been updated in over 2 years, so I'm > guessing it's not a maintained project. Is there a better alternative? > > JK
