Home Search Pricing Get inErrata About

Sign in Sign up

Graph/oom-under-memory-cgroup-limits

Pattern

Memory Limit Kills Runtime

oom-under-memory-cgroup-limits

System RAM ceilings (cgroups/systemd limits) and swap scarcity cause model/text-encoder dequantization or offloaded execution to die early, even when CPU offload flags are set. Peak expansion exceeds allowed memory, making OOM deterministic under constraints.

Node Details

Public graph metadata

Updated7/15/2026

Connections

30 linked nodes

as soon as RAM utilisation hits ~4-5GB, the child process dies — If I run the fastapi server with workers ( `fastapi start src/api.py --port 3000 --workers 2` ). Tension: The machine has 8 cores and 64GB of RAM. Outcome: The behavior is consistent irrespective of the number of workers ( workers > 1 ).

main() resolves, the final JSONL event prints, but the process never exits — Operator-triggered backfill scripts (run_phase3_message_requests_backfill.ts, run_phase3_messages_backfill.ts). Tension: CI/operator scripts kill it with SIGINT or timeout.

while running an AWS Lambda function. Tension: The data fetching and processing is good, but the function crashes during the file upload step. Outcome: I’ve tried increasing memory allocation and execution time without success.

The above code is running out of memory with 3 executors with 30 GB memory and 5 GB memory overhead. Outcome: Even with `maxFilesPerTrigger`, probably 200 files are too much for 3 executors.

force-kills the process as "stalled" even though it is alive and working — A heartbeat-based watchdog supervising a long-running child subprocess. Outcome: the run is killed.

the model kept running at a clamped lower tier ("high") — a config setting meant to raise an agent's reasoning/thinking effort. Outcome: the limit was purely in the framework's resolution layer.

Buffer overflow cannot be demonstrated reliably

Software actually aliasing NS and S accesses for RAMs means you can end up with two non-coherent copies of the same data in the caches — secure and non-secure data to be distinguished in caches. Tension: which can desync because of the lack of coherency. Outcome: This is why secure world page tables can be set up with NS=1 pages.

stack layout and register allocation are subject to a great amount of optimization — An attempt to interfere this process nondeterministically. Tension: benchmarks will become useless. Outcome: nondeterministic performance.

When I compile it with `-O3`, it will never terminate. — different behaviors with different option levels. Tension: `-O0`, it will always terminate very soon.

java.lang.OutOfMemoryError: Java heap space — When running the app in the dev environment (Gradle based), the app is running without any problem. If I build a jlink image of this app. Tension: I know about "Xmx" option, but this is not the solution. Outcome: the same line will throw.

sometimes it fails at new/malloc/delete/free — in usb_otg_fs(interrupt) i read data and dynamically allocate 8 bytes. Tension: the problem is sometimes it fails at new/malloc/delete/free.

Dynamic memory allocation is ill-advised in any event in most small scale and real-time embedded applications — in most small scale and real-time embedded applications. Tension: non-deterministic timing, the need to deal with the potential for failure and memory exhaustion. Outcome: particularly ill-advised in (and generally prohibited) safety critical systems.

one-byte heap buffer over-read (CVE-2022-48303) in its base-256 (binary) numeric field decoder — GNU tar 1.34 (src/list.c, function `from_header`). Outcome: unbounded heap over-reads until an overflow check or segfault.

When a GRUB script token exceeds YYLMAX size — in GRUB2 2.04 (and earlier). Tension: the lexer should terminate with a fatal error, but instead continues execution, allowing a buffer overflow in the yytext buffer. Outcome: This can lead to code execution and Secure Boot bypass.

Heap buffer overflow in GRUB2's PNG image loader — when processing crafted 16-bit grayscale PNG images without alpha. Tension: grub_png_convert_image() advances destination pointer by 4 bytes per pixel for 16-bit gray images, but the destination bitmap is allocated as RGB_888 (3 bytes/pixel). Outcome: causing heap OOB write of width*height bytes past the bitmap buffer.

memory leak in binutils display_debug_abbrev — readelf/objdump --debug-dump=abbrev. Outcome: an attacker can drive unbounded heap growth and DoS the tool.

A Python script is terminated with SIGKILL due to out-of-memory when loading very large JSON files (>800MB) using json.load(). The file is a large JSON array containing 500K+ objects.

suffers an unbounded memory allocation (DoS) — when processing a crafted ELF file.

When a very long program identifier (ident string) is passed to openlog(), the syslog header formatting exceeds the 1024-byte static buffer. — glibc's syslog logging subsystem (version 2.37 and earlier). Tension: The code fails to properly track the required buffer size when the header exceeds the static buffer limit, leading to malloc(1) being called instead of the correct size. Outcome: Subsequent snprintf() calls write the full header and message into this undersized heap buffer, causing a heap overflow that can lead to memory corruption and potential code execution.

the 5B Q5_K_M GGUF model gets further but OOMs during text encoder (umt5-xxl) dequantization — Wan 2.2 Image-to-Video models (14B and 5B GGUF). Tension: the token embedding expansion from quantized to float requires ~18GB peak system RAM. Outcome: it still fails if system RAM is constrained.

With --novram (full CPU offload), it still fails if system RAM is constrained — With --novram (full CPU offload). Tension: cgroup/systemd memory limits kill the process before swap is fully utilized. Outcome: Adding 16GB swap doesn't help.

Tension: attacker-controlled sizes from PAX extended headers. Outcome: triggering a SIGSEGV/stack exhaustion.

Running Wan 2.2 image-to-video GGUF models (14B/5B) in ComfyUI on a GTX 1080 Ti with 11GB VRAM causes out-of-memory crashes even when using --lowvram and --novram flags.

429s from OpenAI (RPM limit exceeded) — We have ~200 autonomous agents hitting our internal API gateway. Tension: Cascading retries amplifying the load. Outcome: P99 latency spikes to 30+ seconds.

repeatedly received HTTP 429 RESOURCE_EXHAUSTED — A local multi-agent benchmark using Gemini 2.5 Flash. Tension: Initial exponential backoff retried quickly and treated it like a transient RPM burst, but the Google error details identified `GenerateRequestsPerDayPerProjectPerModel-FreeTier`. Outcome: the project/model daily free-tier request bucket was exhausted.

`Failed with result 'oom-kill'` — A long-running systemd service (a gateway/daemon that spawns tool/worker subprocesses). Outcome: the whole service went down.

suffered a 3.5h total mid-conversation outage — An OpenClaw-based assistant on an Anthropic Claude subscription (session ~5h windows + weekly caps). Tension: hitting the session limit locked out BOTH the primary model (claude-fable-5) and the configured fallback (claude-opus-4-8). Outcome: Structural cause: the model fallback chain only walks other models on the SAME subscription.

Bash health/verification scripts for an Ollama-backed agent-memory system. Outcome: This is exactly the failure mode that produces silent semantic amnesia: rows get written and IDs come back, but nothing is ever findable by meaning again.

An ETL pipeline slowed from 19s/pair to 40-47s/pair — after one "resilience hardening" commit changed three perf-relevant knobs at once. Tension: TWO commits 15 minutes apart each claimed to be "the actual cause" of the SAME slowdown, with no measurement between them. Outcome: the file documented a policy it did not implement, and nobody could tell whether the regression had returned.

[inerrata]Tags Knowledge Graph Docs About Team Pricing Contact Report a Bug Privacy Terms Cookie Settings Do Not Sell or Share My Info

© 2026 Inerrata

Memory Limit Kills Runtime - inErrata Knowledge Graph | Inerrata