Hi Giovanni,

On components and services there in a ngOnDestroy life-cycle hook. You can 
use this for the teardown. Point to note, browsers might take a while to do 
a complete run of garbage-collection. Especially when there is a lot of 
memory available, it can take quite a while before memory is actually 
released. This is not an angular issue, just the way browsers handle memory 


You received this message because you are subscribed to the Google Groups 
"Angular and AngularJS discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to angular+unsubscr...@googlegroups.com.
To post to this group, send email to angular@googlegroups.com.
Visit this group at https://groups.google.com/group/angular.
For more options, visit https://groups.google.com/d/optout.

Reply via email to