ngOnDestroy for cleanup in Angular - Performance & Optimization

Performance: ngOnDestroy for cleanup

MEDIUM IMPACT

This affects the interaction responsiveness and memory usage by properly cleaning up resources when components are destroyed.

Cleaning up subscriptions and timers when a component is destroyed

Angular

import { Component, OnDestroy } from '@angular/core';
import { Subscription } from 'rxjs';
@Component({ selector: 'app-example', template: '' })
export class ExampleComponent implements OnDestroy {
  subscription: Subscription = someObservable.subscribe();
  timerId = setInterval(() => console.log('tick'), 1000);

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

Properly unsubscribes and clears timers when the component is destroyed, freeing memory and CPU resources.

📈 Performance GainPrevents memory leaks and reduces CPU usage, improving input responsiveness (INP).

Cleaning up subscriptions and timers when a component is destroyed

Angular

import { Component } from '@angular/core';
@Component({ selector: 'app-example', template: '' })
export class ExampleComponent {
  subscription = someObservable.subscribe();
  timerId = setInterval(() => console.log('tick'), 1000);
  // No ngOnDestroy implemented
}

Subscriptions and timers remain active after component destruction, causing memory leaks and unnecessary CPU usage.

📉 Performance CostLeads to increased memory usage over time and can cause input lag (INP) due to background tasks.

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
No cleanup in ngOnDestroy	No direct DOM ops but leaves event listeners active	Triggers extra reflows indirectly due to background tasks	Increases paint cost due to unnecessary JS work	[X] Bad
Proper cleanup in ngOnDestroy	Removes event listeners and timers	No extra reflows triggered	Minimal paint cost, efficient rendering	[OK] Good

Rendering Pipeline

ngOnDestroy runs during the component destruction phase, allowing cleanup before the DOM nodes are removed. This prevents lingering event listeners and timers that could cause unnecessary work during rendering and interaction.

→JavaScript Execution

→Layout

→Paint

⚠️ BottleneckJavaScript Execution due to lingering subscriptions or timers causing extra work

Core Web Vital Affected

INP

This affects the interaction responsiveness and memory usage by properly cleaning up resources when components are destroyed.

Optimization Tips

1Always unsubscribe from observables in ngOnDestroy to prevent memory leaks.

2Clear timers and intervals in ngOnDestroy to avoid unnecessary CPU usage.

3Use DevTools Performance panel to verify no lingering tasks after component destruction.

Performance Quiz - 3 Questions

What is the main performance benefit of implementing ngOnDestroy for cleanup?

A Prevents memory leaks and reduces CPU usage by unsubscribing and clearing timers

B Improves initial page load speed by lazy loading components

C Reduces CSS selector complexity to speed up style calculation

D Minimizes DOM nodes to reduce layout time

DevTools: Performance

How to check: Record a session while navigating away from the component and watch for lingering JavaScript activity or memory usage that does not drop.

What to look for: Look for long tasks or continuous CPU usage after component destruction indicating missing cleanup.

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