Unsubscribing from observables
When we subscribe to an observable, we create an observer that listens for changes in a data stream. The observer watches the stream continuously while the subscription remains active. When a subscription is active, it reserves memory in the browser and consumes certain resources. If we do not tell the observer to unsubscribe at some point and clean up any resources, the subscription to the observable will possibly lead to a memory leak.
An observer usually needs to unsubscribe when the Angular component that has created the subscription needs to be destroyed.
Some of the most well-known techniques to use when we are concerned with unsubscribing from observables are the following:
- Unsubscribe from an observable manually
- Use the
asyncpipe in a component template
Let's see both techniques in action in the following sections.
Destroying a component
A component has life cycle events we can hook on and perform custom logic, as...