Sign in
Skip to solution
hardFrontend

How do you avoid memory leaks from subscriptions?

445 views
01

Understand the problem

Explain unsubscribe patterns.

rxjsunsubscribe
02

Attempt it yourself

Sketch your approach before reading the solution — that's what interviews test.

Nudge consolestandby

Stuck? Beam a request up — the console returns a conceptual nudge that guides your logic without spoiling the implementation.

03

Study the solution

Prefer the async pipe (auto-unsubscribes). For manual subscriptions, unsubscribe in ngOnDestroy, use takeUntil(destroy$), or the modern takeUntilDestroyed() operator. Leaked subscriptions keep components alive and cause memory and duplicate-handler bugs.

Solution ready — 2 min read

Classified // press E to declassify

04

Read the code

takeUntilDestroyed for a long-lived stream
import { Component } from '@angular/core';
import { takeUntilDestroyed } from '@angular/core/rxjs-interop';
import { interval } from 'rxjs';

@Component({ selector: 'app-root', standalone: true, template: '{{ n }}' })
export class AppComponent {
  n = 0;
  constructor() {
    // auto-unsubscribes when this component is destroyed → no leak
    interval(1000)
      .pipe(takeUntilDestroyed())
      .subscribe(v => (this.n = v));
  }
}
05

Join the discussion

Discussion (0)

Sign in to join the discussion.

No responses yet. Be the first to share what you think.

Transmission complete // awaiting log

KEEP THE
STREAK ALIVE.

Dossier 105 of 121 decoded in the Angular track. One more won't hurt.

Back to track