Memory management best practices in Node.js

Introduction

Memory management helps your Node.js app run smoothly without using too much computer memory. It stops your app from slowing down or crashing.

When your app handles many users or big data

When you notice your app is slow or uses a lot of memory

When you want to avoid crashes caused by running out of memory

When you build long-running servers or background jobs

When you want to keep your app stable and fast

Syntax

Node.js

// Example: Using global.gc() to trigger garbage collection
if (global.gc) {
  global.gc();
} else {
  console.log('Run Node.js with --expose-gc to enable manual garbage collection');
}

Node.js automatically manages memory with garbage collection.

You can manually trigger garbage collection only if Node.js is started with --expose-gc.

Examples

Using variables inside functions helps memory get freed when the function ends.

Node.js

// Avoid global variables to prevent memory leaks
function processData() {
  let tempData = [];
  // use tempData inside function
}
processData();

Streams let you process data bit by bit, saving memory.

Node.js

// Use streams to handle large files without loading all in memory
const fs = require('fs');
const readStream = fs.createReadStream('largefile.txt');
readStream.on('data', chunk => {
  console.log('Read chunk:', chunk.length);
});

Stopping timers frees memory and CPU resources.

Node.js

// Clear timers and intervals when no longer needed
const timer = setInterval(() => {
  console.log('Running');
}, 1000);

setTimeout(() => {
  clearInterval(timer);
  console.log('Timer stopped');
}, 5000);

Sample Program

This program reads a file in small parts (chunks) instead of loading it all at once. This way, it uses less memory and stays fast.

Node.js

import fs from 'fs';

// Read a large file using stream to save memory
const readStream = fs.createReadStream('example.txt', { encoding: 'utf8' });

readStream.on('data', (chunk) => {
  console.log(`Received chunk of size: ${chunk.length}`);
});

readStream.on('end', () => {
  console.log('Finished reading file');
});

readStream.on('error', (err) => {
  console.error('Error reading file:', err);
});

Important Notes

Always watch for memory leaks by checking if objects are kept longer than needed.

Use Node.js tools like --inspect and Chrome DevTools to monitor memory usage.

Be careful with global variables and event listeners that never get removed.

Summary

Node.js manages memory automatically but you can help by writing clean code.

Use streams for big data to save memory.

Clear timers and avoid global variables to prevent leaks.

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