From: Dorian Haasler <d.haasler@gmx.at>
Subject: Re: MAXTSIZ vs chromium [Re: ungoogled-chromium-155.0.8059.39: ENOMEM on amd64 -current]
To: ports@openbsd.org, Robert Nagy <robert@openbsd.org>,  Theo de Raadt <deraadt@openbsd.org>, Mark Kettenis <mark.kettenis@xs4all.nl>
Date: Wed, 14 Oct 2026 19:14:14 +0200

On Mon, Oct 12, 2026 at 03:30:12PM +0100, Stuart Henderson wrote:
> On 2026/10/12 15:48, Dorian Haasler wrote:
> >     $ readelf -Wl /usr/local/ungoogled-chromium/ungoogled-chromium
> > 
> > The relevant PT_LOAD segment is:
> > 
> >     Type   Offset      FileSiz      MemSiz       Flg  Align LOAD
> >     0x349e340   0x10228870   0x10228870    E   0x1000
> > 
> > This executable segment has a size of 270,698,608 bytes (258.16 MiB).
> 
> > In sys/arch/amd64/include/vmparam.h:
> > 
> >     #define MAXTSIZ ((paddr_t)256*1024*1024)
> 
> you can bump to the next power of 2 (512*1024*1024), rebuild kernel,
> and see how things go.

I raised MAXTSIZ to 512 MiB, recompiled and booted the kernel, which
fixed the issue with ungoogled-chromium. It is working fine now...