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

On 5/9/26 12:35, Mark Millard wrote:
> On 5/9/26 08:00, Bugs Beastie 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).
> 
> For what assignment of USE_TMPFS= ? tmpfs competes for RAM+SWAP.
> 
> Last that I sampled an example of a USE_TMPFS=all chromium builder in
> poudriere-devel of the time was of chromium-137.0.7151.119:
> 
> Total peak tmpfs: 43.00 GiB (there are multiple tmpfs mounts involved)
> usr/local/ tmpfs:  4.43 GiB
> 
> Those are independent of MAKE_JOBS_NUMBER_LIMIT (or analgous) for
> ALLOW_MAKE_JOBS use. Other builders would have their own tmpfs use over
> the same time.
> 
> As stands, an builder waiting for a jobs to work on holds on to its
> prior tmpfs use for the prior job until it is started or deleted.
> 
> Last that I sampled the Total tmpfs use for chromium builder with
> chromium in TMPFS_BLACKLIST was for: chromium-124.0.6367.60
> (I did not separately also look up usr/local/ back then):
> 
> 8.06 GiB

Actually, I do still have the more recent info for such TMPFS_BLACKLIST
restricted tmpfs use for: chromium-137.0.7151.119 (again),

Total peak tmpfs: 12.72 GiB
usr/local/ tmpfs:  4.42 GiB

> 
> Being in TMPFS_BLACKLIST does not eliminate all the tmpfs use by the
> builder.
> 
>>
>> HTH
>>
>>
> 
> 


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