How to fix npm ERR! code ELIFECYCLE npm ERR! errno 139 npm ERR! Exit status 139 in npm

What this error means

Exit code 139 is calculated as 128 + 11, where 11 is the SIGSEGV (segmentation fault) signal. This error occurs when a process attempts to access memory it's not allowed to access—essentially, a crash at the native code level. In npm contexts, this almost always indicates a native module binary incompatibility. Packages with C++ bindings (like bcrypt, node-sass, sharp, or serialport) ship pre-compiled binaries for specific platforms. When these binaries don't match your system's architecture, libc version, or Node.js version, they crash with a segmentation fault.

Typical symptoms

• Segmentation fault message during npm install or build
• Works locally but crashes in Docker container
• Error occurs specifically with native modules (bcrypt, node-sass, etc.)
• Copying node_modules between different OS causes crashes
• Works on macOS/Windows but fails on Linux (Alpine)
• Crashes during webpack optimization or compilation

Common causes

1. Native module pre-compiled binaries incompatible with target platform
2. Alpine Linux musl libc incompatible with glibc-compiled binaries
3. Node.js version mismatch with compiled native modules
4. Architecture mismatch (x64 vs arm64)
5. Docker container using different OS than where node_modules was created
6. Memory corruption from incompatible shared libraries

How to fix "npm ERR! code ELIFECYCLE npm ERR! errno 139 npm ERR! Exit status 139"

# Rebuild all native modules
npm rebuild

# Rebuild specific problematic package
npm rebuild bcrypt --build-from-source
npm rebuild node-sass --build-from-source

# Remove everything
rm -rf node_modules package-lock.json

# Clear npm cache
npm cache clean --force

# Reinstall
npm install

RUN apk add --no-cache python3 make g++ gcc

RUN apt-get update && apt-get install -y build-essential python3

# Instead of:
FROM node:18-alpine

# Use:
FROM node:18-slim
# or
FROM node:18-bullseye

# Check what Node version the module expects
npm view bcrypt engines

# Switch to compatible version
nvm install 18
nvm use 18

# Reinstall after switching
rm -rf node_modules && npm install

# Copy only package files first
COPY package*.json ./

# Install inside container
RUN npm ci

# Then copy source code
COPY . .

[wsl2]
kernelCommandLine = vsyscall=emulate

Advanced notes

npm install segfault-handler

const SegfaultHandler = require('segfault-handler');
SegfaultHandler.registerHandler('crash.log');

Frequently asked questions

What does "npm ERR! code ELIFECYCLE npm ERR! errno 139 npm ERR! Exit status 139" mean?

Exit code 139 is calculated as 128 + 11, where 11 is the SIGSEGV (segmentation fault) signal. This error occurs when a process attempts to access memory it's not allowed to access—essentially, a crash at the native code level. In npm contexts, this almost always indicates a native module binary incompatibility.

How do I fix "npm ERR! code ELIFECYCLE npm ERR! errno 139 npm ERR! Exit status 139"?

Exit code 139 indicates SIGSEGV (segmentation fault), typically caused by native module binary incompatibilities. Rebuild native modules for your platform or use a compatible base image.

What causes "npm ERR! code ELIFECYCLE npm ERR! errno 139 npm ERR! Exit status 139"?

Native module pre-compiled binaries incompatible with target platform Alpine Linux musl libc incompatible with glibc-compiled binaries Node.js version mismatch with compiled native modules

Is the "npm ERR! code ELIFECYCLE npm ERR! errno 139 npm ERR! Exit status 139" error serious?

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

Related errors

• npm ERR! code ELIFECYCLE npm ERR! errno 143 npm ERR! Exit status 143

  How to fix "Exit status 143 (SIGTERM)" in npm

  MEDIUM

• npm ERR! code ELIFECYCLE npm ERR! errno 137

  How to fix "ELIFECYCLE" exit code 137 in npm

  HIGH

• npm ERR! code ELIFECYCLE npm ERR! errno 2 npm ERR! Exit status 2

  How to fix "ELIFECYCLE errno 2 Exit status 2" in npm

  MEDIUM

• npm ERR! code ELIFECYCLE npm ERR! errno 134 npm ERR! Exit status 134

  How to fix "ELIFECYCLE errno 134 Exit status 134" in npm

  MEDIUM

• npm ERR! code ECONNRESET npm ERR! network socket hang up npm ERR! network This is a problem related to network connectivity.

  How to fix "ECONNRESET" in npm

  MEDIUM

• npm ERR! 429 Too Many Requests

  How to fix "429 Too Many Requests" in npm

  MEDIUM

Official resources & further reading

• 📚npm Official Documentation
• 💬
  Stack Overflow: docker container exit segmentation fault errno 139 exit status 139(Stack Overflow)
• 💬
  Stack Overflow: node js script crashes process finished with exit code 139 interrupted by sign(Stack Overflow)
• 📝
  httptoolkit.com: how to debug node segfaults