How to detect process failed due to out of memory?

[JanMikes]

Sometimes it happens (especially for big codebase) that sub-process is killed due to OOM:

[ 2374.680372] Out of memory: Killed process 10912 (php) total-vm:3659936kB, anon-rss:3551220kB, file-rss:0kB, shmem-rss:0kB, UID:0 pgtables:7156kB oom_score_adj:0

Experienced it on rector sub-process but it can happen for any sub-process: https://github.com/PHPMate/phpmate/blob/master/worker/src/Infrastructure/Symfony/Process/SymfonyProcessRectorBinary.php#L28

Idea is that if this happens, i want to pay extra attention to it, because it can have various outcomes - increase memory, increase swap, optimize process..

Help is wanted - how to detect process failed due to OOM?

[northys]

just buy more ram =)

[JanMikes]

This could be useful resource: https://github.com/grosser/preoomkiller

Idea: if oom killer exited with specific code, it can be detected afterwards

As well have look at /sys/fs/cgroup/memory/memory.usage_in_bytes and /sys/fs/cgroup/memory/memory.stat