doing two things in the same time, so made a mistake . code should be : var orphan = this.parentNode.removeChild(this); delete orphan; // DBJ added delete
I think this might make jQ much slower ? -- DBJ On Apr 20, 1:06 pm, DBJDBJ <[email protected]> wrote: > Actually in the jQ files why can't I/You prefix every call to > removeChild() woth delete ? > > For example: > > delete this.parentNode.removeChild(this); // DBJ added delete > > This should/might improve things .. > > -- DBJ > > On Apr 20, 11:35 am, Danny Tuppeny <[email protected]> wrote: > > > > Ok, I suppose it would not be difficult then to make a simplest > > > possible page that proves this , that we can try from some public > > > url ? > > > Yes, the jQuery homepage shows the problem. Any page including jQuery > > leaks, and the more you use it, the more it'll leak. Point drip here: > > >http://jquery.com > > > > I suppose you have seen this already : > > >http://trac.dojotoolkit.org/ticket/1727 > > > Yes, I've seen that. The suggested fix leaves an empty element in dom > > (and the jquery support code is leaking while trying to avoid exactly > > that) so doesn't help. Furthermore in my tests it didn't actually stop > > the leak :-( --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
