u 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
>
> O
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
I've some news.
The nightly of jquery is not changed in this part (.html())
In the trunk, some changes are done by resig, that resolve the problem
for the .html method, using innerhtml.
So, the clock example is now not leaking at all.
But the .remove methond continue with this:
element.parentNo
> Phaedra, how are you identifying the number of leaked nodes?
I'm using sieve 0.08. I take note of the used nodes in the home page,
then, i open a dialog (jquery), again take note of the nodes.
After closing it they are always there, removed in the dom but
always there in memory. The
> Phaedra, how are you identifying the number of leaked nodes?
I'm using sieve 0.08. I take note of the used nodes in the home page,
then, i open a dialog (jquery), again take note of the nodes.
After closing it the nodes are always there, removed in the dom but
always there in memor
So, no one looking at this topic? or no one know nothing about?
Hi to all, i've a little problem with this script, i can't make it
works in ie.
The problem is that it always opens a new windows when i submit the
upload form, even if i use the target property to a just created
iframe.
In FF, it will target the iframe as expected.
Can you help me?
Here's the
7 matches
Mail list logo