Has Anyone figured this out? It seems to still be happening with angular 1.2.9
i have ng-repeat in a template for a directive. cant figure out how to stop this leak for the life of me! On Tuesday, November 12, 2013 4:32:08 PM UTC-5, Peter McKee wrote: > > I'm seeing the same thing ... any work around? > > It looks like ngRepeat will use a "cache" for the elements placed in the > dom if the object that is reference to it is still in the collection being > watched by the ngRepeat. > > But if compile is run again on ngRepeat, then the "cache" is wiped and the > dom elements are orphaned. I also think that jQuery, at least in my case, > is holding on to them. > > On Sunday, September 15, 2013 10:31:12 AM UTC-5, Michal Kurtak wrote: >> >> Hi, >> >> I have found memory leak when using ng-view with directive with ng-repeat >> in it. I believe it is a bug in angular 1.0.8 and 1.2.0.rc2. Here is a >> sample code http://plnkr.co/5adwl9kwCyxT5urU9D5x >> >> Bug occures when switching between views: >> view1 - view with directive nievents (ng-repeat inside it) >> view2 - empty view >> >> After switching between views several times, i can see Detached DOM tree >> (with 692 entries) with elements from view1, although i am switched to >> view2. When you keep switching again and again, copies of Detached DOM >> trees are created and cause memory leak. >> >> I am not able to determine what causes a memory leak, but I can see >> ng-repeat scopes are not destroyed (parent scopes from controller are >> destroyed). >> >> Tested on Chrome 29.0.1547.66 m but FF is also leaking. >> >> Anyone else encountered the same issue? >> >> Cheers, >> Michal >> >> -- You received this message because you are subscribed to the Google Groups "AngularJS" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/angular. For more options, visit https://groups.google.com/groups/opt_out.
