https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250388
Mark Millard <marklmi26-f...@yahoo.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |marklmi26-f...@yahoo.com
--- Comment #2 from Mark Millard <marklmi26-f...@yahoo.com> ---
(In reply to igor.polovykh from comment #0)
> . . . killed: out of swap space
If your console messasges do not include
messages about "swap_pager_getswapspace(...): failed",
then it is unlikely that being out of swap space
is the actual issue even when it reports: "was killed:
out of swap space" messages. For such contexts, making
the swap area bigger does not help.
In other words, "was killed: out of swap space"
is frequently a misnomer and not to be believed
for "why" the kill happened or what should be
done about it --without other evidence also being
present anyway.
Do you have "swap_pager_getswapspace(...): failed"
notices? The answer would likely guide what sorts
of things would be appropriate to avoid the "killed:
out of swap space" events.
FYI: Other causes of the kill events include . . .
Sustained low free RAM (via stays-runnable processes).
A sufficiently delayed pageout.
The swap blk uma zone was exhausted.
The swap pctrie uma zone was exhausted.
(stays-runnable processes are not swapped out
[kernel stacks are not swapped out] but do actively
compete for RAM via paging activity. In such a
context, free RAM can stay low.)
--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
freebsd-toolchain@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-toolchain
To unsubscribe, send any mail to "freebsd-toolchain-unsubscr...@freebsd.org"
