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
