Process explorer gives you the memory usage per software.
Don t be confuse, I m not talking about the standard window thing under the
task manager, but process explorer (procexp.exe -
http://technet.microsoft.com/en-us/sysinternals/bb896653.aspx)
Download and test it.
If you want more details, you can use javascript memory validator
http://www.softwareverify.com/javascript/memory/index.html (30 days free
eval)
It will give you a detailed use of the memory, showing even when garbage
collection happens.
Unfortunalely it does not work with IE yet.
Of course process explorer does not tell you which node are leaking, but
before to fix, you've to make sure the issue is real, and process explorer
is the best tool for that.
Olivvv
On Thu, Jan 14, 2010 at 12:52 PM, Phaedra phaedra.casa...@gmail.com wrote:
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.
