mirror of
https://github.com/stablyai/orca.git
synced 2026-09-22 08:02:28 +00:00
m4air
5184d92643
Three v1.4.200 field reports (2ea53f9c, ad185d76, 181e8e36) are Arch renderer SIGKILLs with ~100% free swap and gigabytes of MemAvailable, and 181e8e36 lost the GPU process to exit 9 in the same tree. The kernel OOM killer does not fire with that headroom; systemd-oomd, default-enabled on Arch, kills a whole cgroup on PSI memory stall instead. Nothing in the report could tell those apart, or tell either from an outside kill, because /proc/meminfo is the entire Linux memory story a report carried. Read cgroup v2 memory.max/high/current and memory.events (oom_kill, max, high), plus PSI some/full avg10/avg60 from /proc/pressure/memory and the cgroup's own memory.pressure. Both flow through getSystemMemoryDetails, so the existing pre-gone sampler carries them as systemMemoryPreGone* automatically: an oom_kill counter stepping across the death proves the kernel did it, and an unchanged one rules the cgroup out. The Linux pressure signal no longer says 'mem-available' unconditionally — it refines to 'mem-available-cgroup-capped' or 'mem-available-stalled'. Both keep the family prefix, so no existing value changes meaning. Both readers are platform-guarded, swallow every read failure, and stay silent rather than emit a row of zeroes that would read as "measured, and unlimited".