MAX_THREAD_IDS is defined as 128 in a file with a copyright notice of 2005, which was when the very first consumer dual core processors started getting released:<p><a href="https://github.com/perilouswithadollarsign/cstrike15_src/blob/master/tier0/threadtools.cpp#L99" rel="nofollow">https://github.com/perilouswithadollarsign/cstrike15_src/blo...</a><p>Entirely reasonable that no one in 2005 would even consider the possibility of 128 core processors. I bet nobody reconsidered or even looked at that code ever since, until it started breaking because of today's extremely parallel cpus starting to get somewhat affordable for consumers.
><i>"The solution?"</i><p><pre><code> # echo 0 > /sys/devices/system/cpu/cpu{121..127}/online
</code></pre>
><i>"Disabling just one core makes the game start, but then it segfaults when the menu opens. Disabling six cores makes the menu work. Disabling seven makes the rest of the game work too.</i>"<p>What path do you walk to be able to figure out this kind of black magic by yourself?
To be fair, the issue is not that there are too many physical cores, or that someone set that constant to 128. The issue is the code that spawns 1 thread per core doesn't check that constant to limit how many threads it spawns.
I’m not super familiar with cgroups, but I have to assume there’s a parameter for limiting the number of cores available to a process, rather than doing it at the kernel level in /sys