Effective scope for cleanup in Vue - Performance & Optimization

Performance: Effective scope for cleanup

MEDIUM IMPACT

This concept affects how efficiently Vue components release resources and avoid memory leaks, impacting long-term page responsiveness and stability.

Cleaning up event listeners or timers in Vue components

Vue

import { onMounted, onUnmounted } from 'vue';
onMounted(() => {
  window.addEventListener('resize', onResize);
});
onUnmounted(() => {
  window.removeEventListener('resize', onResize);
});

Removes event listener exactly when component unmounts, freeing memory and stopping unnecessary work.

📈 Performance GainPrevents memory leaks and reduces CPU usage, improving interaction responsiveness.

Cleaning up event listeners or timers in Vue components

Vue

import { onMounted } from 'vue';
onMounted(() => {
  window.addEventListener('resize', onResize);
});
// No cleanup on unmount

Event listener stays active after component unmount, causing memory leaks and unnecessary event handling.

📉 Performance CostCauses memory leaks and extra CPU usage on every resize event even when component is gone.

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
No cleanup of event listeners	No direct DOM ops	0	0	[X] Bad
Cleanup in onUnmounted hook	No direct DOM ops	0	0	[OK] Good

Rendering Pipeline

Cleanup code runs during component unmount lifecycle, preventing unnecessary DOM updates and event handling after removal.

→JavaScript Execution

→Event Handling

⚠️ BottleneckExcess event listeners or timers causing unnecessary JavaScript execution

Core Web Vital Affected

INP

This concept affects how efficiently Vue components release resources and avoid memory leaks, impacting long-term page responsiveness and stability.

Optimization Tips

1Always pair resource setup with cleanup in the same component scope.

2Use onUnmounted to remove event listeners and timers.

3Avoid global side effects that persist beyond component lifecycle.

Performance Quiz - 3 Questions

Why is it important to clean up event listeners in Vue components?

A To prevent memory leaks and reduce unnecessary CPU usage

B To make the component load faster initially

C To improve CSS rendering speed

D To reduce the size of the JavaScript bundle

DevTools: Performance

How to check: Record a session while mounting and unmounting the component multiple times; look for increasing memory or event handler counts.

What to look for: Memory usage should stay stable and event listeners count should not grow after repeated mounts/unmounts.

Practice

1. In Vue, which lifecycle hook is best to use for cleaning up timers or event listeners when a component is removed?

easy

A. onUpdated

B. onMounted

C. onUnmounted

D. onCreated

Solution

1. Step 1: Understand Vue lifecycle hooks

   onMounted runs when the component appears, onUnmounted runs when it disappears.

2. Step 2: Identify cleanup timing

   Cleanup like stopping timers or removing listeners should happen when the component is removed, so onUnmounted is the right hook.

3. Final Answer:

   onUnmounted -> Option C

4. Quick Check:

   Cleanup runs on unmount = C [OK]

Hint: Cleanup always goes in onUnmounted hook [OK]

Common Mistakes:

• Using onMounted for cleanup
• Confusing onUpdated with cleanup
• Trying to cleanup in onCreated

2. Which of the following is the correct syntax to register a cleanup function in Vue's setup() using the onUnmounted hook?

easy

A. onUnmounted(() => { clearInterval(timer) })

B. onUnmounted = () => { clearInterval(timer) }

C. onUnmounted.clear(() => { clearInterval(timer) })

D. onUnmounted.clearInterval(timer)

Solution

1. Step 1: Recall Vue hook syntax

   Vue lifecycle hooks like onUnmounted are functions that take a callback to run on that event.

2. Step 2: Match correct syntax

   The correct way is calling onUnmounted with a function: onUnmounted(() => { ... }). Other options misuse assignment or methods.

3. Final Answer:

   onUnmounted(() => { clearInterval(timer) }) -> Option A

4. Quick Check:

   Hook usage = function call with callback [OK]

Hint: Hooks are called with a function, not assigned [OK]

Common Mistakes:

• Assigning instead of calling onUnmounted
• Using nonexistent methods on onUnmounted
• Missing arrow function wrapper

3. What will be the console output when this Vue component unmounts?

setup() {
  const timer = setInterval(() => console.log('tick'), 1000)
  onUnmounted(() => clearInterval(timer))
}

medium

A. Logs 'tick' only once when component unmounts

B. Logs 'tick' every second until component unmounts, then stops

C. No logs appear at all

D. Throws an error on unmount

Solution

1. Step 1: Understand setInterval behavior

   setInterval logs 'tick' every 1000ms continuously until cleared.

2. Step 2: Analyze cleanup with onUnmounted

   When the component unmounts, clearInterval(timer) stops the interval, so logging stops after unmount.

3. Final Answer:

   Logs 'tick' every second until component unmounts, then stops -> Option B

4. Quick Check:

   Interval runs until cleared on unmount [OK]

Hint: Intervals run until cleared in onUnmounted [OK]

Common Mistakes:

• Thinking logs stop immediately without unmount
• Expecting logs only once on unmount
• Assuming error on clearInterval

4. Identify the problem in this Vue setup function and how to fix it:

setup() {
  const timer = setInterval(() => console.log('tick'), 1000)
  onMounted(() => clearInterval(timer))
}

medium

A. Cleanup runs too early; should use onUnmounted instead

B. Timer is never created; setInterval is missing

C. clearInterval is called without timer variable

D. No problem; code works correctly

Solution

1. Step 1: Check when cleanup runs

   Using onMounted to clear interval means it stops immediately after mounting, so no ticks happen.

2. Step 2: Correct cleanup timing

   Cleanup should happen when component unmounts, so onUnmounted is the correct hook to clear the timer.

3. Final Answer:

   Cleanup runs too early; should use onUnmounted instead -> Option A

4. Quick Check:

   Cleanup must be on unmount, not mount [OK]

Hint: Cleanup belongs in onUnmounted, not onMounted [OK]

Common Mistakes:

• Clearing timer on mount instead of unmount
• Assuming onMounted is for cleanup
• Ignoring lifecycle hook purpose

5. You have a Vue component that subscribes to a WebSocket in setup(). Which pattern correctly ensures the subscription is cleaned up only when the component unmounts?

setup() {
  const socket = new WebSocket('wss://example.com')
  socket.onmessage = (event) => console.log(event.data)
  // What cleanup code and where?
}

hard

A. Call socket.close() immediately after creating socket

B. No cleanup needed for WebSocket in Vue

C. Use onMounted(() => socket.close()) to close socket on mount

D. Use onUnmounted(() => socket.close()) inside setup

Solution

1. Step 1: Understand WebSocket lifecycle

   WebSocket stays open until closed; closing it too early stops messages.

2. Step 2: Place cleanup in onUnmounted

   To avoid leaks, close the socket when component unmounts using onUnmounted(() => socket.close()).

3. Final Answer:

   Use onUnmounted(() => socket.close()) inside setup -> Option D

4. Quick Check:

   Cleanup subscriptions on unmount with onUnmounted [OK]

Hint: Close subscriptions in onUnmounted hook [OK]

Common Mistakes:

• Closing socket immediately after creation
• Closing socket on mount instead of unmount
• Skipping cleanup causing memory leaks