Date: Thu, 17 Dec 2020 08:58:14 +0000 From: bugzilla-noreply@freebsd.org To: toolchain@FreeBSD.org Subject: [Bug 251886] clang: error: clang frontend command failed due to signal Message-ID: <bug-251886-29464-GsdRHu9xKY@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-251886-29464@https.bugs.freebsd.org/bugzilla/> References: <bug-251886-29464@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D251886 --- Comment #9 from Mark Millard <marklmi26-fbsd@yahoo.com> --- (In reply to igor.polovykh from comment #7) If you can repeat the failure, do you get any interesting console log messages ( /var/log/messages content ) during the build? Does top show low free RAM? Swap nearly all in use? If you do get one or more "was killed: out of swap space" messages: Be warned that the "out of swap space" part can be a misnomer. Only if you also see message(s) with text of the form "swap_pager_getswapspace(...): failed" is the swap space part of the notice the actual cause as far as I know. Other causes 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. There are tunables for some of that that make some of those not trip as soon ( /etc/sys.conf content ): # # Delay when persistent low free RAM leads to # Out Of Memory killing of processes. The # delay is a count of kernel-attempts to gain # free RAM (so not time units). vm.pageout_oom_seq=3D120 (The default is 12 as far as I know.) NOTE: stable/12 -r351776 got the support for the following: (I've not checked the match to releases.) # # For plunty of swap/paging space (will not # run out), avoid pageout delays leading to # Out Of Memory killing of processes: vm.pfault_oom_attempts=3D-1 That last has the alternative structure (replace ???'s with positive integers): # # For possibly insufficient swap/paging space # (might run out), increase the pageout delay # that leads to Out Of Memory killing of # processes: #vm.pfault_oom_attempts=3D ??? #vm.pfault_oom_wait=3D ??? # (The multiplication of the two values is the # total but there are other potential tradoffs # in the factors multiplied for the same total.) For reference: # sysctl -d vm.pfault_oom_wait vm.pfault_oom_wait: Number of seconds to wait for free pages before retrying the page fault handler # sysctl -d vm.pfault_oom_attempts vm.pfault_oom_attempts: Number of page allocation attempts in page fault handler before it triggers OOM handling # sysctl -d vm.pageout_oom_seq vm.pageout_oom_seq: back-to-back calls to oom detector to start OOM --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-251886-29464-GsdRHu9xKY>