Memory management best practices in Node.js - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is garbage collection in Node.js?

Garbage collection is the automatic process where Node.js frees up memory by removing objects that are no longer needed or referenced in the program.

beginner

Why should you avoid global variables in Node.js for memory management?

Global variables stay in memory for the lifetime of the application, which can cause memory to be used unnecessarily and lead to memory leaks.

intermediate

How can you detect memory leaks in a Node.js application?

You can use tools like Chrome DevTools, Node.js built-in inspector, or third-party modules to monitor memory usage and find objects that keep growing without being released.

intermediate

What is the benefit of using streams in Node.js for memory management?

Streams process data in small chunks instead of loading everything into memory at once, which reduces memory usage and improves performance.

intermediate

Explain the role of the 'heap' and 'stack' in Node.js memory management.

The stack stores simple, short-lived data like function calls and variables, while the heap stores objects and data that can grow dynamically. Efficient use of both helps manage memory well.

Which of the following helps prevent memory leaks in Node.js?

A Avoiding global variables

B Using synchronous file reads only

C Ignoring unused objects

D Disabling garbage collection

Avoiding global variables helps prevent memory leaks because globals stay in memory for the app's lifetime.

What Node.js feature processes data in chunks to save memory?

A Callbacks

B Promises

C Streams

D Events

Streams handle data in small parts, reducing memory use compared to loading all data at once.

Which tool can you use to inspect memory usage in Node.js?

A Chrome DevTools

B Git

C NPM

D Webpack

Chrome DevTools can connect to Node.js to inspect memory and debug leaks.

What does garbage collection do in Node.js?

A Manually frees memory

B Automatically frees unused memory

C Increases memory usage

D Prevents code execution

Garbage collection automatically frees memory that is no longer used.

Where are objects stored in Node.js memory?

A Register

B Stack

C Cache

D Heap

Objects are stored in the heap, which handles dynamic memory allocation.

Describe three best practices to manage memory effectively in a Node.js application.

Think about how to keep memory usage low and detect problems early.

Explain how garbage collection works and why it is important in Node.js.

Consider how Node.js cleans up memory without programmer intervention.

Practice

1. Which of the following is a good practice to help Node.js manage memory efficiently?

easy

A. Use streams to process large data instead of loading it all at once

B. Keep all data in global variables for easy access

C. Avoid using asynchronous functions to reduce complexity

D. Never clear timers or intervals once set

Solution

1. Step 1: Understand memory usage with large data

   Loading large data all at once uses a lot of memory. Streams process data in small chunks, saving memory.

2. Step 2: Evaluate options for memory efficiency

   Using global variables or never clearing timers can cause memory leaks. Avoiding async functions doesn't help memory.

3. Final Answer:

   Use streams to process large data instead of loading it all at once -> Option A

4. Quick Check:

   Streams save memory by chunking data [OK]

Hint: Streams handle big data efficiently, avoid globals [OK]

Common Mistakes:

• Thinking global variables are memory efficient
• Ignoring the need to clear timers
• Believing async functions cause memory leaks

2. Which syntax correctly clears a timeout timer in Node.js to prevent memory leaks?

easy

A. clearTimeout(timerId);

B. clearInterval(timerId);

C. stopTimer(timerId);

D. removeTimer(timerId);

Solution

1. Step 1: Identify the correct function to clear a timeout

   Node.js uses clearTimeout() to stop timers set by setTimeout().

2. Step 2: Match function to timer type

   clearInterval() clears intervals, not timeouts. stopTimer() and removeTimer() are invalid.

3. Final Answer:

   clearTimeout(timerId); -> Option A

4. Quick Check:

   clearTimeout() stops setTimeout timers [OK]

Hint: Use clearTimeout for setTimeout timers [OK]

Common Mistakes:

• Confusing clearTimeout with clearInterval
• Using non-existent functions like stopTimer
• Not clearing timers at all

3. What will be the output of the following code snippet regarding memory usage?

const data = [];
setInterval(() => {
  data.push(new Array(1000000).fill('x'));
  console.log('Data length:', data.length);
}, 1000);

medium

A. Data length stays at 1, memory usage is stable

B. Data length increases indefinitely, causing memory to grow

C. Throws an error after first interval

D. Data length resets to zero every second

Solution

1. Step 1: Analyze the setInterval behavior

   Every second, a large array is added to the data array, increasing its size.

2. Step 2: Understand memory impact

   Since data keeps growing without clearing, memory usage grows indefinitely, risking leaks.

3. Final Answer:

   Data length increases indefinitely, causing memory to grow -> Option B

4. Quick Check:

   Growing arrays without cleanup increase memory [OK]

Hint: Adding large arrays repeatedly grows memory [OK]

Common Mistakes:

• Assuming data length resets automatically
• Expecting an error without memory limits
• Thinking memory stays stable without cleanup

4. Identify the memory leak issue in this Node.js code:

let cache = {};
function addToCache(key, value) {
  cache[key] = value;
}
setInterval(() => {
  addToCache(Date.now(), new Array(1000000).fill('leak'));
}, 1000);

medium

A. Arrays are too small to cause memory issues

B. Using Date.now() as key causes syntax error

C. The cache object grows indefinitely without cleanup

D. setInterval is cleared automatically, no leak

Solution

1. Step 1: Examine cache growth

   Each second, a new large array is added with a unique key, so cache size grows endlessly.

2. Step 2: Understand memory leak cause

   Without removing old entries, memory usage increases causing a leak.

3. Final Answer:

   The cache object grows indefinitely without cleanup -> Option C

4. Quick Check:

   Uncleared caches cause memory leaks [OK]

Hint: Uncleared caches with growing keys leak memory [OK]

Common Mistakes:

• Thinking Date.now() causes syntax errors
• Assuming setInterval clears itself
• Underestimating array size impact

5. You have a Node.js app that processes large files. Which combined approach best prevents memory leaks and high memory use?

hard

A. Process files in memory, use setInterval without clearing, and avoid streams

B. Load entire files into memory, keep global caches, and never clear timers

C. Use synchronous file reads, keep data in global variables, and clear timers

D. Use streams to process files, clear timers after use, and avoid global caches

Solution

1. Step 1: Choose memory-efficient file processing

   Streams process large files in chunks, reducing memory use compared to loading whole files.

2. Step 2: Manage timers and caches properly

   Clearing timers prevents leaks. Avoiding global caches stops memory from growing endlessly.

3. Final Answer:

   Use streams to process files, clear timers after use, and avoid global caches -> Option D

4. Quick Check:

   Streams + clear timers + no globals = best memory practice [OK]

Hint: Combine streams, clear timers, avoid globals for best memory [OK]

Common Mistakes:

• Loading full files into memory
• Not clearing timers causing leaks
• Using global caches without cleanup