[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/4a99f6e9b2e33057/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
[jQuery] Re: Advice on sIEve/Drip?
An important aspect of this is to focus on what happens when you reload the page or navigate away. If the memory drops back down to its original state, you have helped the end user by not leaving them a legacy of used memory. It's much more difficult to try and keep memory from climbing in the first place. If you can make it so the memory is reclaimed when you unload the page, you have gone a long way in helping the user. -- Josh - Original Message - From: trixta [EMAIL PROTECTED] To: jQuery (English) jquery-en@googlegroups.com Sent: Wednesday, November 05, 2008 6:14 AM 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/4a99f6e9b2e33057/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
[jQuery] Re: Advice on sIEve/Drip?
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
[jQuery] Re: Advice on sIEve/Drip?
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
[jQuery] Re: Advice on sIEve/Drip?
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
[jQuery] Re: Advice on sIEve/Drip?
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? Arrgh. JK -Original Message- From: jquery-en@googlegroups.com [mailto:[EMAIL PROTECTED] On Behalf Of mattkime Sent: Monday, November 03, 2008 1:16 PM To: jQuery (English) Subject: [jQuery] Re: Advice on sIEve/Drip? 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
[jQuery] Re: Advice on sIEve/Drip?
*bump* 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
