[Bug 287549] When some process grows too large system kills its small parent processes which ends the process itself and causes more damage

From: <bugzilla-noreply_at_freebsd.org>
Date: Sat, 14 Jun 2025 19:21:40 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=287549

            Bug ID: 287549
           Summary: When some process grows too large system kills its
                    small parent processes which ends the process itself
                    and causes more damage
           Product: Base System
           Version: 14.2-STABLE
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: kern
          Assignee: bugs@FreeBSD.org
          Reporter: yuri@freebsd.org

I run the build of lang/rust-nightly on a 24GB 14.2-STABLE amd64 machine which
is started from the XFCE4 terminal in the XFCE4 desktop environment.

The build spawns several large Rust compiler processes. They together exceed
24GB at some point. The system then decides to kill the tiny (in comparison)
XFCE4 terminal process, which destroys all other work in this terminal.

The above behavior doesn't make sense. Killing a small parent process doesn't
really address the memory issue, and causes more damage than killing the
offending processes themselves.

The right behavior would be one of three:
(1) to find and kill some larger leaf process that doesn't contain the
offending processes as their children
(2) kill the offending processes themselves
(3) just keep running with large processes competing for memory, in a hope that
they would get out of that phase eventually

-- 
You are receiving this mail because:
You are the assignee for the bug.