Re: Memory problems at build time

On Jan 25 2023, Adam Majer wrote:

This is kind of this legacy mechanism that is used to prevent the local build from blowing up and stalling your machine (which doesn't always work anyway). But, if you run NodeJS with webassembly, it will allocate a whole 4GB address space for every instance, even if it uses just a few bytes. So when you run a few of these concurrently, like in the nodejs unit tests, it will go past the `ulimit` set with the above error.

That limit is per-process, though, so the number of instances is not relevant for this particular limit. -- Andreas Schwab, SUSE Labs, schwab@suse.de GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7 "And now for something completely different."