I'm not so sure to understand how to use process explorer this way, a memory increase/decrease is not always significant.
I don't think pm can tell me how many nodes are leaking On 14 Gen, 12:35, Olivier Percebois-Garve <perceb...@gmail.com> wrote: > Hi > > To make sure that a leak is a leak, you should better use process explorer > first (http://technet.microsoft.com/en-us/sysinternals/bb896653.aspx). > Sieve tends to leak by himself. Sieve is only good at giving you indication > of where the bug might come from, but it should not be trusted too much... > > Olivvv > > On Thu, Jan 14, 2010 at 12:21 PM, Phaedra <phaedra.casa...@gmail.com> wrote: > > As subject said, i've tried the new release of jquery in a real single > > page environnement, and it leaks again and again when trying to remove > > elements, with or without events attached. > > > When i add a node to the dom, it correctly add 1 node instead of 2 > > (older versions of jquery), but when i try to remove it, ie not > > releasing it from memory. > > > Using sieve to test it.
