on ninja: the “brunch” inside the build script will grab all the cores, and using 16 will put too much memory pressure on the system until oom comes around. If you’d not build from docker you could influence the thread count of make.
(but now that the ccache is filled, maybe a second build will go through anyway?)
You can create your own build image as in Modifying a prebuilt Docker image and mount an alternative build-script that splits the brunch into breakfast + mka bacon -jX where X is a lesser core count, 12 or 8
Edit: no need to modify the image when you can also mount the modified build script from the outside. Newer versions of the buildscript upstream do offer parallel threads as environment variable