There was a big game that took more than the current 2G.
With 3G all seems well.

Fine cranking in-tree or should I just use a local wrapper?

Index: games/0ad/base/Makefile
===================================================================
RCS file: /cvs/ports/games/0ad/base/Makefile,v
diff -u -p -r1.52 Makefile
--- games/0ad/base/Makefile	21 May 2024 01:29:18 -0000	1.52
+++ games/0ad/base/Makefile	12 Jun 2024 15:52:53 -0000
@@ -2,7 +2,7 @@ COMMENT =		historical real-time strategy
 
 DISTNAME =		0ad-${V}-alpha-unix-build
 PKGNAME =		0ad-${V}
-REVISION =		7
+REVISION =		8
 
 USE_WXNEEDED =		Yes
 USE_NOBTCFI =		Yes
Index: games/0ad/base/patches/patch-build_resources_0ad_sh
===================================================================
RCS file: /cvs/ports/games/0ad/base/patches/patch-build_resources_0ad_sh,v
diff -u -p -r1.1 patch-build_resources_0ad_sh
--- games/0ad/base/patches/patch-build_resources_0ad_sh	21 May 2024 01:29:18 -0000	1.1
+++ games/0ad/base/patches/patch-build_resources_0ad_sh	12 Jun 2024 15:53:26 -0000
@@ -1,4 +1,4 @@
-Try to crank datasize to 2G to avoid ENOMEM crashes during big games
+Try to crank datasize to 3G to avoid ENOMEM crashes during big games
 
 Index: build/resources/0ad.sh
 --- build/resources/0ad.sh.orig
@@ -7,7 +7,7 @@ Index: build/resources/0ad.sh
  
  pyrogenesis=$(which pyrogenesis 2> /dev/null)
  if [ -x "$pyrogenesis" ] ; then
-+  DATASIZE=$((2 * 1024 * 1024))
++  DATASIZE=$((3 * 1024 * 1024))
 +  if [ $(ulimit -Sd) -lt ${DATASIZE} ]; then
 +    ulimit -Sd ${DATASIZE} || \
 +      ${X11BASE}/bin/xmessage -file - -center -buttons yes:0,no:1 -default no <<- _EOF