> There's not much to clean up as far as I understood the OP

Yup. It's stuff from within the jQuery source, even if we don't run
any code. But where to clean them up isn't really the problem - it's
how they can actually be cleaned up. Some of the things causing leaks
(eg. the root.removeChild(script) call) are there to remove things
that were added to the DOM to test browser capabilities. They can't be
left there (who wants random elements on their page created by
jQuery?), but removing them just seems to cause leaks.

This is a pretty serious issue for us - our app seems to be leaking a
*lot* (we are using jQuery heavily and doing a *lot* of DOM
manipulation in our app). Every single element leaked in our app
appears to come from the jQuery source - they're mostly empty divs.
There are quite a few places within the jQuery source (eg. offset)
that create divs and remove them with removeChild (which leaks them in
IE). I suspect 90% of them will be fixable in the same way. I just
can't find a nice way to remove the divs without leaking. There's some
stuf fon the web suggesting you can move things into a div then set
it's innerHTML to an empty string. This would still leave an
additional div in the dom, but on top of that, it doesn't seem to work
in my tests!

If anyone has any ideas (either short term hacks or proper fixes that
could be put into the jQuery source), please do share!

If I come up with anything I'll post back here.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"jQuery Development" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/jquery-dev?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to