How to fix FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - JavaScript heap out of memory in Node.js

What this error means

This error indicates that your Node.js application has exhausted its allocated heap memory and cannot allocate additional memory for JavaScript objects. Node.js has a default maximum heap size (typically 512MB on 32-bit systems and around 1.4GB on 64-bit systems) as a V8 engine limitation. When your application tries to allocate memory beyond this limit, V8's garbage collector attempts multiple times to free up space (the "CALL_AND_RETRY_LAST" phase), and when all attempts fail, the process terminates with this fatal error. The error is particularly common during memory-intensive operations like building large applications with webpack or similar tools, processing large datasets, or when memory leaks cause gradual memory accumulation over time.

Typical symptoms

• Application crashes immediately with a fatal error message
• Process terminates during build steps (webpack, vite, rollup)
• Error occurs when processing large files or datasets
• Application runs fine initially but crashes after extended operation
• Memory usage steadily increases until crash (visible in monitoring tools)
• Error appears during npm/yarn build or compilation steps

Common causes

1. Default Node.js heap size is insufficient for your application's memory requirements
2. Memory leaks from unreleased references, unclosed connections, or circular dependencies
3. Processing large files or datasets entirely in memory without streaming
4. Build tools (webpack, vite) requiring more memory than allocated for bundling
5. Accumulation of cached data without proper cleanup mechanisms
6. Large dependency trees causing excessive memory consumption during installation
7. Recursive operations without tail-call optimization consuming stack space
8. System memory pressure from other running processes limiting available RAM

How to fix "FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - JavaScript heap out of memory"

# Set heap size to 4GB (4096 MB)
node --max-old-space-size=4096 app.js

# For npm scripts, add to package.json
"scripts": {
  "start": "node --max-old-space-size=4096 server.js",
  "build": "node --max-old-space-size=4096 node_modules/.bin/webpack"
}

# Linux/macOS
export NODE_OPTIONS="--max-old-space-size=4096"
npm run build

# Windows (PowerShell)
$env:NODE_OPTIONS="--max-old-space-size=4096"
npm run build

# Windows (cmd)
set NODE_OPTIONS=--max-old-space-size=4096 && npm run build

export NODE_OPTIONS="--max-old-space-size=4096"

ENV NODE_OPTIONS="--max-old-space-size=4096"

NODE_OPTIONS=--max-old-space-size=4096

# Run with inspector enabled
node --inspect app.js

# Or with explicit memory monitoring
node --inspect --trace-gc app.js

npm install -g clinic
clinic doctor -- node app.js

// Bad: loads entire file into memory
const data = fs.readFileSync('large-file.json', 'utf8');
const json = JSON.parse(data);

// Good: streams data in chunks
const stream = fs.createReadStream('large-file.json');
const parser = JSONStream.parse('*');
stream.pipe(parser);
parser.on('data', (chunk) => {
  // Process each chunk
});

// Bad: loads all records
const allRecords = await db.users.findMany();

// Good: processes in batches
const pageSize = 100;
let page = 0;
while (true) {
  const records = await db.users.findMany({
    skip: page * pageSize,
    take: pageSize
  });
  if (records.length === 0) break;
  // Process records
  page++;
}

// Use WeakMap for automatic garbage collection
const cache = new WeakMap();

// Explicitly null out large objects when done
largeObject = null;

// Bad: event listener never removed
eventEmitter.on('data', handler);

// Good: remove when done
eventEmitter.on('data', handler);
// Later...
eventEmitter.removeListener('data', handler);

// Better: use once() for single-use listeners
eventEmitter.once('data', handler);

// Clear intervals and timeouts
const interval = setInterval(() => {}, 1000);
// Later...
clearInterval(interval);

// Use AbortController for cleanup
const controller = new AbortController();
eventEmitter.on('data', handler, { signal: controller.signal });
// Later...
controller.abort(); // Removes all listeners

// Bad: creates circular reference
const obj1 = {};
const obj2 = { ref: obj1 };
obj1.ref = obj2; // Circular reference

// Good: avoid or break circular references
obj1.ref = null; // Break the cycle when done

module.exports = {
  mode: 'production',
  optimization: {
    minimize: true,
    usedExports: true, // Tree shaking
    splitChunks: {
      chunks: 'all', // Split large bundles
      cacheGroups: {
        vendor: {
          test: /[\\/]node_modules[\\/]/,
          name: 'vendors',
          chunks: 'all'
        }
      }
    }
  },
  // Reduce memory usage during builds
  stats: 'errors-only',
  performance: {
    hints: false
  }
};

export default {
  build: {
    rollupOptions: {
      output: {
        manualChunks(id) {
          if (id.includes('node_modules')) {
            return 'vendor';
          }
        }
      }
    }
  }
};

Advanced notes

Frequently asked questions

What does "ENOMEM" mean?

js application has exhausted its allocated heap memory and cannot allocate additional memory for JavaScript objects. 4GB on 64-bit systems) as a V8 engine limitation. When your application tries to allocate memory beyond this limit, V8's garbage collector attempts multiple times to free up space (the "CALL_AND_RETRY_LAST" phase), and when all attempts fail, the process terminates with this fatal error.

How do I fix "ENOMEM"?

This fatal error occurs when a Node.js process attempts to allocate more memory than the available heap size allows. The process crashes because it cannot continue execution without the requested memory allocation.

What causes "ENOMEM"?

Default Node.js heap size is insufficient for your application's memory requirements Memory leaks from unreleased references, unclosed connections, or circular dependencies Processing large files or datasets entirely in memory without streaming

Is the "ENOMEM" error serious?

Yes. This is a critical-severity error that usually blocks work until it is fixed, but the steps above resolve it.

Related errors

• Error: ENOTDIR: not a directory, scandir '/path/to/file.txt'

  ENOTDIR: not a directory, scandir

  MEDIUM

• Error: ENOENT: no such file or directory, open 'file.txt'

  How to fix "ENOENT: no such file or directory" in Node.js

  MEDIUM

• Error: ENOTEMPTY: directory not empty, rmdir 'dirname'

  ENOTEMPTY: directory not empty when removing directory

  MEDIUM

• Error: ENODEV: no such device, read

  ENODEV: no such device, read

  HIGH

• Error: zlib error Z_DATA_ERROR (corrupted compressed data)

  Z_DATA_ERROR: Corrupted compressed data

  MEDIUM

• Error: Could not find package.json in current directory (npm module resolution)

  How to fix "Could not find package.json in current directory" in Node.js

  MEDIUM

Official resources & further reading

• 📚Node.js Official Documentation
• 📖
  Node.js CLI Options - Official Documentation(Official Docs)
• 🔗
  How to fix "fatal reached heap limit allocation failed javascript heap out of memory" - DEV Community
• 🔗
  Understanding and Resolving the "FATAL ERROR: JavaScript heap out of memory" Issue - Medium
• 🔗
  How to Fix JavaScript Heap Out of Memory Error - Flexiple
• 🔗
  Solved: How to Fix "JavaScript Heap Out of Memory Error" - Geekflare
• 🐙
  Allocation failed - JavaScript heap out of memory - Next.js Discussion(GitHub)