Memory Leak: boxSizingReliable about jquery HOT 4 CLOSED

Thanks for opening an issue. As noted in your other issue, retaining something this small should not cause problems. Intentionally retaining a variable is not the same as a memory leak. A memory leak is when a particular operation continues to increase memory, but here there is only ever one element retained. The question is, does this cause a real world issue? It's so small I don't see how.

Anyway, the container element is no longer on the main branch. There is still a div and it is no longer nulled, but its purpose goes a bit beyond the support test.

from jquery.

Understood but in chrome it forces a whole tree of things to be retained according to the heap dump.

from jquery.

@melloware can you provide more details about this tree?

We’re all for solving real memory issues but we first need to know there’s a real one.

BTW, we cannot call computeStyleTests() eagerly; we spent a lot of effort in jQuery 1.11/2.1 to make sure support tests that trigger layout are done lazily for performance reasons.

from jquery.

@mgol i totally understand. I think locally I just need to build a debug Jquery version that does this. I came to this because I am helping a client debug client side memory leaks and their Detached DOM keeps growing so I am trying to filter out real issues from noise.

No worries leave this closed and thanks for the responsiveness!

from jquery.