Why ngOnDestroy for cleanup in Angular? - Purpose & Use Cases

The Big Idea

What if your app could clean up its mess all by itself when you leave a page?

The Scenario

Imagine you create a component that listens to user actions or data streams. When you leave that component, you forget to stop those listeners or subscriptions.

The Problem

Without proper cleanup, your app keeps running old listeners in the background. This wastes memory, slows down your app, and can cause strange bugs that are hard to find.

The Solution

Angular's ngOnDestroy lets you run cleanup code automatically when a component is removed. This stops listeners and frees resources, keeping your app fast and bug-free.

Before vs After

✗ Before

componentDidLeave() { /* forgot to unsubscribe from data stream */ }

✓ After

ngOnDestroy() { this.subscription.unsubscribe(); }

What It Enables

You can build smooth, efficient apps that clean up after themselves without extra effort.

Real Life Example

Think of a chat app where each chat window listens for new messages. When you close a chat, ngOnDestroy stops the message listener so your app stays quick and responsive.

Key Takeaways

Manual cleanup is easy to forget and causes bugs.

ngOnDestroy runs cleanup code automatically.

This keeps your Angular app fast and reliable.

Practice

1. What is the main purpose of the ngOnDestroy lifecycle hook in Angular?

easy

A. To handle user input events

B. To initialize component data when it is created

C. To run cleanup code when a component or directive is removed

D. To render the component template

Solution

1. Step 1: Understand the role of ngOnDestroy

   The ngOnDestroy hook is called when Angular removes a component or directive from the view.

2. Step 2: Identify its main use

   It is used to clean up resources like timers, subscriptions, or event listeners to avoid memory leaks.

3. Final Answer:

   To run cleanup code when a component or directive is removed -> Option C

4. Quick Check:

   ngOnDestroy = cleanup [OK]

Hint: Remember: ngOnDestroy cleans up before component removal [OK]

Common Mistakes:

• Confusing ngOnDestroy with ngOnInit
• Thinking it initializes data
• Assuming it handles user events

2. Which of the following is the correct way to implement ngOnDestroy in an Angular component?

easy

A. destroy() { console.log('Component destroyed'); }

B. ngOnDestroy = () => { console.log('Component destroyed'); }

C. function ngOnDestroy() { console.log('Component destroyed'); }

D. ngOnDestroy() { console.log('Component destroyed'); }

Solution

1. Step 1: Recall Angular lifecycle hook syntax

   Angular lifecycle hooks are methods inside the component class with exact names like ngOnDestroy().

2. Step 2: Check method declaration style

   The correct syntax is a method, not an arrow function or standalone function, and must be named exactly ngOnDestroy.

3. Final Answer:

   ngOnDestroy() { console.log('Component destroyed'); } -> Option D

4. Quick Check:

   ngOnDestroy method syntax = ngOnDestroy() { console.log('Component destroyed'); } [OK]

Hint: Use method syntax named exactly ngOnDestroy [OK]

Common Mistakes:

• Using arrow functions for lifecycle hooks
• Naming method incorrectly
• Defining lifecycle hook outside class

3. Consider this Angular component code snippet:

export class TimerComponent implements OnDestroy {
  intervalId = setInterval(() => console.log('tick'), 1000);

  ngOnDestroy() {
    clearInterval(this.intervalId);
    console.log('Timer stopped');
  }
}

What will happen when this component is removed from the view?

medium

A. The interval stops and logs 'Timer stopped' once

B. An error occurs because clearInterval is not valid here

C. Nothing happens because ngOnDestroy is not called automatically

D. The interval keeps running and logs 'tick' every second

Solution

1. Step 1: Understand what ngOnDestroy does here

   When the component is removed, Angular calls ngOnDestroy, which clears the interval timer.

2. Step 2: Effect of clearing the interval

   Clearing the interval stops the repeated 'tick' logs, and the message 'Timer stopped' is logged once.

3. Final Answer:

   The interval stops and logs 'Timer stopped' once -> Option A

4. Quick Check:

   ngOnDestroy clears timer = The interval stops and logs 'Timer stopped' once [OK]

Hint: ngOnDestroy stops timers to prevent leaks [OK]

Common Mistakes:

• Thinking interval keeps running after destroy
• Assuming ngOnDestroy is not called
• Confusing clearInterval usage

4. You have this Angular component:

export class DataComponent implements OnDestroy {
  subscription = this.dataService.getData().subscribe();

  ngOnDestroy() {
    this.subscription.unsubscribe;
  }
}

What is the problem with this code?

medium

A. The unsubscribe method is not called correctly

B. The subscription is never created

C. ngOnDestroy is missing the return type

D. There is no problem; code works fine

Solution

1. Step 1: Check how unsubscribe is used

   The code uses this.subscription.unsubscribe; without parentheses, so the method is not actually called.

2. Step 2: Correct usage of unsubscribe

   It should be this.subscription.unsubscribe(); to properly stop the subscription and avoid memory leaks.

3. Final Answer:

   The unsubscribe method is not called correctly -> Option A

4. Quick Check:

   Call unsubscribe() with parentheses [OK]

Hint: Always call unsubscribe() as a function [OK]

Common Mistakes:

• Forgetting parentheses on unsubscribe
• Assuming unsubscribe is a property
• Ignoring ngOnDestroy lifecycle

5. You have a component that subscribes to multiple observables and sets up an event listener:

export class MultiCleanupComponent implements OnDestroy {
  sub1 = this.service1.getData().subscribe();
  sub2 = this.service2.getData().subscribe();

  constructor() {
    window.addEventListener('resize', this.onResize);
  }

  onResize() {
    console.log('Window resized');
  }

  ngOnDestroy() {
    // What should be done here?
  }
}

Which is the best way to clean up all resources in ngOnDestroy?

hard

A. Only call this.sub1.unsubscribe(); this.sub2.unsubscribe();

B. Call this.sub1.unsubscribe(); this.sub2.unsubscribe(); window.removeEventListener('resize', this.onResize);

C. Only call window.removeEventListener('resize', this.onResize);

D. No cleanup needed because Angular handles it automatically

Solution

1. Step 1: Identify all resources to clean

   The component has two subscriptions and an event listener on the window.

2. Step 2: Proper cleanup in ngOnDestroy

   To avoid memory leaks, unsubscribe both subscriptions and remove the event listener using removeEventListener.

3. Final Answer:

   Call this.sub1.unsubscribe(); this.sub2.unsubscribe(); window.removeEventListener('resize', this.onResize); -> Option B

4. Quick Check:

   Unsubscribe and remove listeners in ngOnDestroy [OK]

Hint: Clean all subscriptions and listeners in ngOnDestroy [OK]

Common Mistakes:

• Forgetting to remove event listeners
• Only unsubscribing some observables
• Assuming Angular cleans up automatically