How to fix Segmentation fault (core dumped) in Node.js

# List all native modules
find node_modules -name "*.node" -type f | head -20

# Or use npm to list packages with native addons
npm list --depth=0 | grep -E '(node-gyp|native|addon)'

# Clear npm cache
npm cache clean --force

# Rebuild all native modules
npm rebuild

# Or rebuild a specific module
npm rebuild module-name

# Update all packages
npm update

# Or update a specific native module
npm install module-name@latest

# Check outdated packages
npm outdated

# List your dependencies
npm list --depth=0

# Remove suspicious modules one at a time
npm uninstall problematic-module

# Run your app and test
node your-app.js

# On Linux, increase core dump limit
ulimit -c unlimited

# Run your Node.js app
node your-app.js

# A "core" file will be created if a crash occurs
# Analyze with gdb
gdb node core
# In gdb, type: backtrace
# This shows where in the native code the crash occurred

npm install segfault-handler

import segfaultHandler from 'segfault-handler';

// Setup handler at the very beginning
segfaultHandler.registerHandler('crash.log');

// Rest of your app code
import express from 'express';
const app = express();
// ... your code

# Check your current version
node --version

# Install a specific LTS version using nvm
nvm install 20  # Latest LTS

# Switch to it
nvm use 20

# Rebuild native modules for new version
npm rebuild

# Get more details about the crash (if core dump is available)
# Search the affected module's GitHub issues
# Example: If crash is with 'sqlite3'
# Visit: https://github.com/mapbox/node-sqlite3/issues
# Search for "segmentation fault" or "SIGSEGV"