pls see attached pstree - at least ninja ignores it, although the tinderbox set this:
Created attachment 526316 [details]
Patch #1 from patchset in bug #630834 should fix this problem.
Your attachment shows that src/3rdparty/chromium/tools/gn/bootstrap/bootstrap.py was run and exactly this file is changed by sed in the aforementioned patch.
*** Bug 666270 has been marked as a duplicate of this bug. ***
Created attachment 561864 [details]
this is from qt-webengine-5.11.3, where 13 c++ processes are spawned
*** Bug 683776 has been marked as a duplicate of this bug. ***
I have encountered this bug on a 4-core system with only 1GB of ram (and 8 GB of swap). At times there were 6 instances of cc1plus, and the system was swapping so hard I could barely open top or even kill the compilation.
This seems to be an issue with the way ninja is allocating resources on the build system for maximum performance: https://github.com/ninja-build/ninja/issues/1441
Is there a way, any way, to force ninja to stop fork bombing my computer? Even if it is forced to run in a throttled sandbox of some kind?
FWIW these settings here seems not to be enough but might be a starting point: