Re: firefox-158.0 build failure NetBSD 11.0-STABLE

[Greg Troxel <gdt%lexort.com@localhost>]

Mike Pumford <mpumford%mudcovered.org.uk@localhost> writes:

> Ran into a similar issue with one of my own nodejs projects and it
> looks like the real underlying issue here is the max data segment size
> that I have in login.conf.
>
> nodejs sizes the heap based on the max data segment size set by
> ulimit. Which I had set to a tiny 512MB meaning nodejs ended up with a
> 256MB heap. Not unreasonable given the ulimit in play so I guess the
> ultimate fix is a ulimit -d wrapped around my build script.

That is reasonable of node.  512 MB of data size is super small, on a
machine that has a lot more memory.

I have 4GB datasize on a machine with 5GB of RAM, and 8GB on one with
32GB.  I get it that you're trying to protect some processes from
others, and there is no easy one-size-fits-all answer.