Hi All; I also am facing similar issue. I have used jquery libraries for charts with angular. My Application is single page application with multiple view using slide menu. One thing i noticed is as follow:
1) When page is changed it doesn't free memory. Even i have tried implimenting destroy method and cleaning up controllers object lying in $scope. 2) When changing data in same page (using buttons), it does free-up the memory. I even have tried one clear button to clean object lying in $scope, it does free-up the memory. But when i go to another page, it does not free-up memory used by the object even after cleaning controllers object on destroy method. Is there any solution to this?? On Tuesday, April 1, 2014 11:12:29 PM UTC+5:30, Kai Groner wrote: > > Some of this is to be expected. Any directive that uses transclusion, > will have a copy of those elements ready to be cloned and attached as > needed. That's any ng-if, ng-repeat (1 copy, not n), ng-switch, ng-include > (I think) to name a few. > > Figuring out if some of these are actually leaks will require some > accounting to determine where the markup is being compiled from. I don't > know if there are tools that can help with this, or if you have to > instrument the $compile service by hand. > > > Kai > > > > On Tue, Apr 1, 2014 at 12:11 AM, Stephen Kawaguchi <[email protected] > <javascript:>> wrote: > >> Have either of you had any luck tracking down the source of the problem? >> My setup is more complex where the culprit could be a number of things >> (using jQuery, hammer.js, bindonce, custom directives), but I'm hoping that >> your experience could help narrow it down a bit. Any help is much >> appreciated! >> >> >> On Tuesday, January 21, 2014 1:25:51 AM UTC-5, Ryan Swart wrote: >>> >>> I'm also suffering from detached DOM trees, and object properties that >>> cling on to them. I'm not manually manipulating the DOM, just using Jquery, >>> ng-repeat and a couple of ng-shows and hides >>> >>> >>> <https://lh6.googleusercontent.com/-CM6Lx49vMeo/Ut4MXJtDFHI/AAAAAAAAFik/UxeO2DYmcm0/s1600/snapshot1.png> >>> >>> I'm wondering if it hasn't got something to do with Jquery's data-cache >>> >>> On Tuesday, October 15, 2013 4:15:03 PM UTC+8, Ryan Zec wrote: >>>> >>>> Another example of an AngularJS application with lots of detached DOM >>>> trees >>>> >>>> http://www.plnkr.co/ >>>> >>>> This applications using AngularJS. If you go to this site and profile >>>> it in chrome and then click on the Most Starred, Recent, Trending, and >>>> Most >>>> Viewed links and then profile it again, the number of detached DOM tree >>>> increases a little and the new detached DOM trees have a large number of >>>> entries in them. >>>> >>>> If this was solely a jQuery issue I would expect these detached DOM >>>> trees to show up for code only using jQuery however the plugins I have >>>> tested don't show this level of detached DOM trees (one of them had 2 >>>> detached DOM trees with a total of 5 entries) so I have to assume it has >>>> to >>>> be something do to with AngualrJS and jQuery/jgLite. >>>> >>> -- >> 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] <javascript:>. >> To post to this group, send email to [email protected] >> <javascript:>. >> Visit this group at http://groups.google.com/group/angular. >> For more options, visit https://groups.google.com/d/optout. >> > > -- 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/d/optout.
