Re: www/chromium 148.0.7778.96 compile failure on 14.3-RELEASE-p11

On 5/9/26 12:25, brianharveyos wrote:
> The chromium project has been known to eat up absurd amount of ram during compilation. Obviously that cascades into swap space as well. I’ve read reducing cores doing compilation will reduce the memory use. Do you know how many you’re compiling with now? It may be helpful to try a smaller amount such as `-j2`

-j2 controls how many builder jobs poudriere-devel uses, not how many
make jobs such a builder job may use (ALLOW_MAKE_JOBS in a
poudreire.conf and MAKE_JOBS_NUMBER_LIMIT or related variations in a
make.conf or Makefile) --nor how many threads there can be active an any
time in any builder or in any make job (no direct means of control in
poudriere(-devel)).

There are other configuration setting that also can greatly change the
amount of competition for RAM+SWAP, commonly the choice for USE_TMPFS=
in a poudriere.conf file and possible use of TMPFS_BLACKLIST there as well.

> 
> - Accidentally replied to only George instead of the thread
> 
> 
> Sent from Proton Mail for iOS.
> 
> -------- Original Message --------
> On Saturday, 05/09/26 at 10:01 Bugs Beastie <[email protected]> wrote:
> May 9, 2026 14:52:53 George Mitchell <[email protected]>:
> 
>> On 5/9/26 08:47, George Mitchell wrote:
>>> On 5/8/26 16:08, George Mitchell wrote:
>>>> On 5/8/26 16:06, George Mitchell wrote:
>>>>> I wasn't running under script, so I can't find the exact failure.  I
>>>>> will run it again more under script.  And I'll file a bug.   -- George
>>>> World version is 14.3-RELEASE-p13, and the kernel will be 14.3-RELEASE-
>>>> p13 after next reboot (yes, stupid move on my part but that's the
>>>> situation at the moment).
>>> Build log available at https://m5p.com/~george/typescript.xz
>>> There's an unhelpful "FAILED" message at line 54473.  It's not at all
>>> clear to me exactly what failed.                              -- George
>> Found this in my system log:
>>
>> May  8 19:45:25 sullivan kernel: swap_pager: out of swap space
>> May  8 19:45:25 sullivan kernel: swp_pager_getswapspace(2): failed
>> May  8 20:04:10 sullivan kernel: swp_pager_getswapspace(3): failed
>> May  8 20:04:12 sullivan kernel: swp_pager_getswapspace(13): failed
>> May  8 20:04:20 sullivan kernel: pid 40641 (clang-22), jid 0, uid 0, was killed: failed to reclaim memory
>> May  8 20:04:21 sullivan kernel: pid 40645 (clang-22), jid 0, uid 0, was killed: failed to reclaim memory
>> May  8 20:04:22 sullivan kernel: pid 40643 (clang-22), jid 0, uid 0, was killed: failed to reclaim memory
>>
>> But it's hard to believe.  I've never run out of swap space on this
>> machine before.                                          -- George
> 
> Hi!
> 
> From my experience safe level is 64 Gb of virtual space (RAM+SWAP) for the build of (ungoogled-)chromium with 4 build threads (-j4).
> 
> HTH
> 
> 
> 
> 


-- 
===
Mark Millard
marklmi at yahoo.com