Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

No process-level heap cap: OOM aborts (rc 134); sandbox max_bytes misses general growth

Abierto
  • ¿Algo no está bien?
#1,319 1 comentario 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
35/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
c
Área
compilers, documentation

Línea de trabajo

Start by reading docs/PRINCIPLES.md and the existing sandbox_run max_bytes behavior, then trace the eigs_alloc chokepoint and run the supplied OOM reproduction. Compare the proposed cap, error, charging, and trace behavior with the sandbox requirements. Done includes a catchable named error, non-134 exit, stopped sandbox growth, a clean handles_full.eigs run, overhead measurements, and synchronized updates to docs/SPEC.md, docs/BUILTINS.md, docs/EMBEDDING.md, and docs/llms.txt.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

area:embed area:memory kind:decision

Gap

There is no process-level heap cap. An embedder, a CI harness or an agent running generated .eigs cannot bound a whole run's memory. The only tools are OS limits, and both are poor fits:

  • ulimit -v (RLIMIT_AS) counts reserved address space, not use. Each thread reserves an 8 MiB stack and a 64 MiB malloc arena up front. Measured in #1318: tests/handles_full.eigs peaks at 21 MB RSS, yet it was killed under a 1.5 GB -v cap. That produced false one-sided rows in a differential harness.
  • cgroups (systemd-run -p MemoryMax=, container limits) work, but they end in a SIGKILL from outside. The program never sees an error, and the harness cannot tell an OOM from a crash without extra machinery.

When memory does run out, the runtime aborts. Repro on main 94c4c5b:

xs is []
s is "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"
i is 0
loop while i < 100000000:
    xs is append of [xs, s + (str of i)]
    i is i + 1
print of "done"

$ ( ulimit -v 300000; src/eigenscript oom.eigs; echo rc=$? )
eigenscript: out of memory (requested 64 bytes)
Aborted (core dumped)
rc=134

sandbox_run's max_bytes is the one budget that exists (#739), and it has two limits:

  1. It is reachable only from inside a program, around an assembled chunk. It cannot cover a whole run.
  2. It charges only the size-controlled allocators (zeros/fill/buffer/range/concat) and the zlib codecs. General growth like the append loop above is not charged, so even a sandboxed run can exhaust the host.

Prior art (for the decision)

  • Runtime-level heap caps that raise a named error: JVM -Xmx (OutOfMemoryError), V8 --max-old-space-size, the allocator limit in Lua's lua_newstate, wasm max memory pages.
  • Harness-level RSS monitors: libFuzzer -rss_limit_mb reports OOM as its own outcome.
  • AFL documents that its RLIMIT_AS limit (-m) must be none under ASan, which is the same failure as above.

Decision needed

  • The knob: an env flag (EIGS_MAX_HEAP=<bytes>, parsed like the other eigs_env_flag knobs), a CLI flag, an embed API field, or all three.
  • What gets charged: every eigs_alloc (a chokepoint charge, which catches the append loop), or live bytes net of frees (which needs the counter decremented on free).
  • What happens at the cap: an rt_error of a new kind (catchable by try, a clean exit code distinct from 134), and what the trace tape records.
  • Whether sandbox_run's max_bytes becomes the same mechanism scoped to the run, which would close its second limitation above.

Done when

  • The decision above is recorded in this issue, citing a principle from docs/PRINCIPLES.md.
  • Running the repro above with the cap set to 64 MiB ends in a named, documented error with a non-134 exit code, and the program can catch it with try.
  • The same program under sandbox_run with max_bytes set is stopped by the budget. It returns {ok: 0}, and the host does not abort.
  • tests/handles_full.eigs runs clean under a cap well above its measured peak (for example 64 MiB), proving thread reservations are not charged.
  • Measured overhead with the cap unset is recorded, taken from the perf-attribution paired samples or the CodSpeed instruction count on the DMG target.
  • docs/SPEC.md, docs/BUILTINS.md (sandbox_run), docs/EMBEDDING.md and docs/llms.txt describe the knob, all in the same PR.
Lenguaje dominante
C
Estrellas
3
Forks
7
Merge medio
4 h 15 min
PR fusionados (30 d)
106

Preparar el entorno

Abrir en Codespaces

Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de InauguralSystems/EigenScript

Todos los issues de InauguralSystems/EigenScript

Issues similares

Más issues de C

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.