Request: more robust memory profiling

[ghost]

ng-stats is a good start on an "internal memory profiler". I've been trying to track down a memory leak in 10,000 lines of Angular app code + 50,000 lines of JavaScript libs. Using "external" profilers like Chrome Dev Tools is ok, but it doesn't given me exactly what I want.

I want something that registers whenever an Angular object is created and then again when it is released.

Requesting that ng-stats is built out to do a more comprehensive dump:

1. What User App objects (Controllers, Services, Directives, Watches, Listeners) have been allocated.
2. Where they were allocated: function names!
3. If they were released.
4. If they are duplicates, ex: more than 1 copy of MyController is in memory.

Maybe list:

1. De-attached DOM objects

[kentcdodds]

Good ideas. It seems to me like these features should be a part of batarang. I have an issue asking @btford if he wants to include ng-stats stuff in batarang (basically just the watch count and digest length stuff, which is all ng-stats is really).

I may or may not have the time to bring these requests into ng-stats, but honestly, I think all of this should go into a single tool that all angular developers use (a.k.a. batarang).