Regres: Increase MaxProcMemory to 6 GiB
Increasing the maxComputeWorkGroupInvocations to 256 revealed that we're
consuming a lot of memory with the Subzero JIT for compute shaders that
contain control barriers, due to implementing them with the use of
fibers which each have a 1 MiB stack.
Increasing Regres's maximum memory consumption per process keeps the
tests passing while we work on a more long-term solution.
Bug: b/192475710
Change-Id: I027d97d9f28d9749628fc008fe956fd436c77562
Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/55368
Kokoro-Result: kokoro <noreply+kokoro@google.com>
Tested-by: Nicolas Capens <nicolascapens@google.com>
Reviewed-by: Corentin Wallez <cwallez@google.com>
diff --git a/tests/regres/shell/shell.go b/tests/regres/shell/shell.go
index 48c68db..2d45398 100644
--- a/tests/regres/shell/shell.go
+++ b/tests/regres/shell/shell.go
@@ -25,7 +25,7 @@
// MaxProcMemory is the maximum virtual memory per child process.
// Note: This is not used on Windows, as there is no sensible way to limit
// process memory.
-var MaxProcMemory uint64 = 4 * 1024 * 1024 * 1024 // 4GB
+var MaxProcMemory uint64 = 6 * 1024 * 1024 * 1024 // 6 GiB
// Shell runs the executable exe with the given arguments, in the working
// directory wd.
