https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=257314
--- Comment #26 from Mark Millard <[email protected]> --- (In reply to Michael from comment #12) I'll note that when the kernel kills a process, that process might leave behind a *.core file as a consequence. But it is not the *.core that caused the kill, it was the kill that lead to the *.core : things were bad at the system level before the *.core happened. For a: kernel: pid ??? (???), jid ???, uid ??, was killed: out of swap space the *.core produced (if any) is likely not the thing of direct interest for evidence about the overall system level status that lead to the kill. The kill sequence goes after bigger processes first, working toward smaller processes later (not that the process sizes are static during this). So the sequence: chrome, gimp-2.10, chrome, chrome, plasmashell, chrome, chrome, Xorg in the Description is suggestive of the relative sizes of the processes around the time of each kill. That the chrome subsequence had pids of (in order) 1551, 1546, 1574, 1548, 1786 shows that the (roughly decreasing?) size was not in the order oldest (1546) to newest (1786). -- You are receiving this mail because: You are the assignee for the bug.
