This article demystifies Linux memory management by explaining why buffers and cache are not meant to be manually cleared, how the 'available' metric differs from 'free', and which sysctl parameters and cgroup settings you should tune to optimize performance and avoid OOM incidents.
This article systematically explains why Linux processes may disappear, covering OOM Killer, signal termination, cgroup limits, systemd timeouts, manual kills, and provides step‑by‑step diagnostic commands and preventive measures for RHEL, AlmaLinux, and Ubuntu environments.
This article explains how Linux memory watermarks, kswapd, direct reclaim, and the OOM Killer interact, provides detailed code examples, shows real‑world case studies, and offers practical tuning steps—including kernel parameters, cgroup limits, and monitoring tools—to prevent system stalls and crashes.
This article explains why memory leaks act like invisible thieves that gradually fill the RSS space, outlines their four‑step attack process, shows how to spot the tell‑tale signs using process‑level and system‑level metrics, and provides practical emergency and preventive measures to protect your applications.
This article explains why the java.lang.OutOfMemoryError: Kill process (java) or sacrifice child occurs, outlines system‑level memory‑shortage causes, and provides practical steps to prevent, fix, and troubleshoot the issue on Linux‑based Java applications.
This article explains how Linux manages memory through page reclamation, detailing the role of LRU algorithms, page classification, reverse mapping, direct and asynchronous reclaim paths, and the OOM killer, while providing code examples and practical tuning advice.
Linux’s OOM Killer activates when memory is exhausted, scoring processes based on usage, priority, and kernel settings, then terminating the highest‑scoring one; the article explains its background, scoring algorithm, influencing parameters, and practical steps such as adjusting oom_score_adj, optimizing memory use, and using cgroups to safeguard essential services.
This article explains the Linux OOM (Out‑Of‑Memory) mechanism, details how the kernel selects and kills the most memory‑hungry process, and shows practical steps to protect critical services from being terminated.
This article explains common memory errors, lists kernel and user‑space event sources for tracing memory activity, and demonstrates how to use BPFTrace, kprobes, and USDT probes to detect out‑of‑bounds accesses, use‑after‑free, memory leaks, OOM killer events, mmap/brk usage, shared memory operations, page faults, and reclaim processes on Linux.
A port alarm revealed a missing Java process, which was later traced to an OOM kill triggered by vim loading a 37 GB nginx log into an 8 GB container, illustrating how editor behavior and Linux's OOM killer can unexpectedly terminate critical services.
The Java service crashed when the Linux OOM killer terminated its process after a developer opened a 37 GB log file with Vim, which loaded the entire file into the container’s 8 GB memory, triggering a port alarm and prompting investigation and recommendations to use streaming tools instead of Vim.
This article explains the Linux OOM Killer’s trigger and selection process, walks through the key kernel functions and heuristics that choose a victim process, and clarifies why out‑of‑memory conditions occur under different overcommit settings.
This article explains Linux virtual memory, the page‑fault allocation process, the two memory‑reclaim paths (kswapd and direct reclaim), OOM killer scoring, swappiness tuning, NUMA‑aware reclamation, and practical steps to protect critical processes from being killed.
This article explains Linux virtual memory concepts, the process of memory allocation, page fault handling, background and direct memory reclamation methods, LRU-based page types, NUMA considerations, tuning parameters like swappiness and min_free_kbytes, and strategies to prevent OOM killer termination.
This article examines why MySQL instances are often targeted by the Linux OOM killer, explains proper InnoDB buffer pool sizing, introduces memory leak concepts, and demonstrates how to use Valgrind's Memcheck tool to detect leaks and improve database memory management.
This article investigates why virtual machines on an OpenStack IaaS platform experience OOM‑killer terminations despite reserved host memory, analyzes memory usage patterns of qemu‑kvm processes, and proposes practical solutions to mitigate unexpected OOM events.
A detailed case study reveals how an out‑of‑memory (OOM) situation on a Linux server caused Tomcat to crash during load testing, explains the kernel's OOM killer behavior, and provides practical solutions such as enabling swap and tuning Apache limits.
A early‑morning alarm revealed a Plumbr service outage caused by the Linux OOM killer terminating a Java process after memory overcommit, disabled swap, and a traffic spike, and the article explains the root cause, reproduces the issue with code, and offers mitigation strategies.
