also looking at this
fix: allow runtime arenas within a finite runner address budget
#7
13 files
+298
-12
| @@ -442,7 +442,17 @@ TYPESENSE_API_KEY=pantry-dev | ||
| 442 | 442 | # these stop is the ordinary accident: a loop that writes a forty-gigabyte |
| 443 | 443 | # file, a build that spins a core forever. Generous on purpose, because a limit |
| 444 | 444 | # that trips on ordinary work is one an operator removes. |
| 445 | # CI_STEP_MEMORY_MB=8192 | |
| 445 | # Despite the legacy name, this ceiling is virtual address space in MiB | |
| 446 | # (`RLIMIT_AS`), not RSS or physical RAM. The finite default is 2 TiB. | |
| 447 | # Chrome's sandbox reserves about 1 TiB plus guard regions; the former 8 GiB | |
| 448 | # default stopped startup. Reserving addresses does not allocate that much RAM. | |
| 449 | # See [V8's sandbox documentation](https://v8.dev/blog/sandbox). | |
| 450 | # | |
| 451 | # Explicit values remain honored, including smaller caps and 0 to disable this | |
| 452 | # ceiling. An existing explicit 8 GiB cap can still prevent Chrome from starting. | |
| 453 | # macOS ignores this address-space limit. Resident-memory accounting and isolation | |
| 454 | # require separate OS controls; this setting does not provide them. | |
| 455 | # CI_STEP_MEMORY_MB=2097152 | |
| 446 | 456 | # CI_STEP_FILE_SIZE_MB=32768 |
| 447 | 457 | # |
| 448 | 458 | # Off by default and worth understanding before setting: both count something |