Best Fixes
Check whether the process was OOM-killed by the kernel or container runtime, then inspect memory limits and usage patterns.
If not memory-related, identify which supervisor, orchestrator, or manual action sent the kill signal.
Error Fix
How to Fix Exit Code 137
Why processes die with signal-based termination and how to tell OOM kills from explicit stops.
Exit code 137 usually means the process received SIGKILL. In containers and CI, that often points to memory pressure, but it can also come from an orchestrator or operator killing the process directly.
Avoid This
Do not assume every 137 exit is an application bug without checking resource limits first.
Do not raise memory limits blindly if the process behavior is actually pathological.
Save commands, add notes, and build a Cheatbook with the fixes you want to keep handy.