This might help: https://www.youtube.com/watch?v=L3ugr9BJqIs
And this (if you haven't seen it): http://addyosmani.com/blog/taming-the-unicorn-easing-javascript-memory-profiling-in-devtools/ It would be extrememly helpful if the google dev relations/angular team produced a vid specifically aimed at angular profiling, showing an app with high memory usage / poor performance and coersing it down to something managable, addressing detached DOM tree and performance in general along the way, with specific memory management/performance improvement tips. Perhaps either on the angular youtube channel or here at 'The Breakpoint': https://www.youtube.com/playlist?list=PLVUliVBcvz1n_DOgB4lb06G_Dc5fQVRRv For me, my focus has been on the question: Are detached DOM trees the cause of memory growth? A significant number of detached dom notes all point to jqCache / JQLite.cache, which makes sense as the Cache is holding elements for ng-* directives. The path to detached DOM tree in my case is: transclude...ng*WatchAction (e.g. ngIfWatchAction or ngWatchCollectionAction)...JQLite.cache Some other questions on this topic: http://stackoverflow.com/questions/1462649/jquery-memory-leak-with-dom-removal?rq=1 http://stackoverflow.com/questions/16901759/javascript-memory-leaks-detached-dom-tree?rq=1 http://stackoverflow.com/questions/19361890/detached-dom-tree-with-angularjs-jquery http://stackoverflow.com/questions/18521254/cant-seem-to-cleanup-detached-dom-elements On Wednesday, October 22, 2014 11:50:46 AM UTC+1, Sean Amoroso wrote: > > Is there any documentation that can describe how ng-view and other ng-* > components handle memory allocation? I am using the 3 snapshot technique > to track down some memory leaks and it is very difficult to determine if > angular is keeping something in cache or it is a true memory leak. > > I am running chrome with the following command line args: Chrome > --user-data-dir=~/tmp/chrome-temp-profile --no-first-run > --js-flags="--nocrankshaft --noopt" > > In theory if I load a view, take a heap snapshot, load a second view, take > a heap snapshot, then load the first view again and snapshot, I should be > able to see what memory has leaked and remains in snapshot 3 that was > allocated between snapshot 1 and 2. However, numerous things remain and I > want to be sure I understand fully what I'm looking at. > > Anyone? Thanks. > > -- 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.
