foreign-builders: Allow 256 MiB of shared memory #203
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
By default, Docker limits containers to using 64 MiB of shared memory. This is a problem for dolphin-emu/dolphin#13768, which calls MemoryManager::Init as part of a unit test. Under Dolphin's default configuration (GameCube without accurate MMU emulation), MemoryManager::Init allocates 32 MiB of shared memory for main RAM, 32 MiB of shared memory for fake VMEM, and 256 KiB of shared memory for the locked L1 cache, which in total is just above Docker's limit.
To solve this, specify 256 MiB as the limit instead of using the default 64 MiB. This should be enough shared memory for MemoryManager even with the MEM1 and MEM2 size override settings maxed out.
This is untested!