TRANSCLUDE MEMORY LEAK: Memory leak with transclusion, ng:repeat and jQuery

[benoitgrelard]

Hi there,

I believe I have found a memory leak in a very specific use case it seems as it only happens when transcluding ng:repeat generated elements and ONLY if jQuery is loaded.

Here is a use case: http://jsbin.com/nirubi/11/edit?html,js,output

You can try everything first with only jQlite. Follow the number of active scopes and active watches.
Then uncomment the jQuery script tag and try again, you'll see that the number of active scopes and watches creeps up in the case of ng:repeat and ONLY when jQuery is being loaded.

Let me know if I'm doing something wrong or if it's a genuine bug.

Thanks!

[petebacondarwin]

@mzgol - any thoughts on this?

[benoitgrelard]

Hi, additional info, this doesn't happen only with jquery's latest (2.x). We have this issue currently in our app which uses jQuery 1.10.2

[petebacondarwin]

Just to be clear this is only related to 1.2.x and not 1.3.x?

[benoitgrelard]

Interestingly, I have just tried the same example with the latest 1.3.x of angular and the problem is actually worse, as it happens WITH or WITHOUT jquery being loaded. But still only in the case of ng:repeat being used.

[petebacondarwin]

Hmm that is not good.

[petebacondarwin]

Here is the jsbin with latest master: http://jsbin.com/lisodiwuluzo/1/edit?html,js,output

[petebacondarwin]

So the scopes seem to go up by 7 when the ng-if is true and down by only 1 when it is false.
And the watches go up by 6 and down by 0 each time

[petebacondarwin]

Problem with ng-if - ng-if combo too: http://jsbin.com/zimuvo/1/edit

[petebacondarwin]

I have a feeling that some of the recent performance changes have a role to play here, such as b5f7970#diff-a732922b631efed1b9f33a24082ae0dbL1036
cc/ @IgorMinar