Diagnosing Docker Container Restart Loops from OOM Kills (Exit 137)
Exit code 137 means the kernel OOM killer stopped your container. Learn how to confirm the cause, inspect memory limits, and apply targeted fixes.
Loading…
ReadMeFeed / Community knowledge
#memory-limits
Real questions. Useful conversations. Find the people who know your stack.
dockerDiagnosing Docker Exit Code 137: Tracing OOM Kills from Container to Host
Exit code 137 means SIGKILL, usually from the kernel OOM killer. Learn to tell a too-low container limit from host memory pressure, and apply the right fix for each.
Diagnosing DuckDB Memory Spills and External Sort Diagnostics
When DuckDB queries fail with out-of-memory errors or sudden slowdowns from external sorting, this guide walks you through recognizing the condition, diagnosing with EXPLAIN ANALYZE, and applying targeted fixes.
duckdb
Fine‑Grained Memory Limits with Linux cgroups v2: Hard, Soft, and Minimum Floors
When running containers on Linux, cgroups v2 lets you enforce precise memory limits. This guide shows how to set hard, soft, and minimum thresholds, demonstrates a practical setup, and warns against common pitfalls.
Deterministic Transaction Termination Under dbms.memory.transaction.total.max
Context Neo4j exposes two memory‑capability knobs: dbms.memory.transaction.max limits each transaction’s heap usage, while dbms.memory.transaction.total.max caps the cumulative heap of all concurrent transactions. When the total limit is exceeded, Neo4j aborts a transaction and rolls it back, but the Operations Manual does not specify which transaction is ch
neo4jOpenCL 3.0 optional SVM support limits portable zero-copy sharing
A design goal is to define portable limits for zero-copy host-device buffer sharing across OpenCL 3.0 implementations without assuming optional features. Device limits for allocation size and base address alignment are device-specific and must be queried at runtime. CL_MEM_USE_HOST_PTR and CL_MEM_ALLOC_HOST_PTR have implementation-defined requirements for po
openclCustodian memory limit accounting varies by Racket backend
Designing per-evaluation resource containment in Racket with custodians and racket/sandbox requires a memory cap that reliably triggers an out-of-memory condition inside the contained computation while leaving the host process intact. The documented mechanism uses custodian-limit-memory and call-with-limits/with-limits. Memory accounting is described as appr
racketLarge snapshot deserialization memory limits in Vitest
Vitest snapshot testing compares serialized output against stored baseline files using toMatchSnapshot . When verifying recovered data after schema changes, large baseline files can increase memory pressure during the test runner's deserialization phase. The specific memory threshold at which Vitest encounters exhaustion during snapshot deserialization is no