Hi Chetan, Without the right context, this screendump say's nothing. Are those component controllers, or normal controllers? During the record of the timeline, did you open and close parts of the application that init's and destroy's those? And so on, and so on. Memory profiling is a challenge in itself, let alone from a screendump.
If those are directive-controllers, it is normal that there are multiple instances (Assuming you reused thise in the view). Google for "detect memory leak in chrome" for some help full pointers. If there is a memory leak, it's probably not caused by angular 1.x, but by another 3rth party, or your own code. Regards Sander -- You received this message because you are subscribed to the Google Groups "Angular" 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 https://groups.google.com/group/angular. For more options, visit https://groups.google.com/d/optout.
