IS there any profile tools to find out exact place where the memory leak is happening ?
Thanks, Delli/
IS there any profile tools to find out exact place where the memory leak is happening ?
Thanks, Delli/
From my experience is not possible to show you exactly part of the code which can be added to garbage collection. In general I test a part of my app (a view) make "heap snapshot" and try to eliminate one by one test again and like that find the code with problem.
Also if you use strict mode with a lint, is a good change to don't have problems.
The above point is for JS in general, for Angular in particular, you know have some specific problems, like: watchers, $timeout, $rootScope, etc.
You can check John Papa style guide here this will help you to avoid some problems.