gap CLI heap still grows during a klona run after #61 (87 to 821 MB after GC; unattributed)
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
- 18/100
- Tipo de issue
- Error
- Claridad
- Bastante claro
- Estado de actividad
- Activo
- Stack tecnológico
- javascript, node.js, vite
- Área
- cli, performance, tooling
Línea de trabajo
Start in packages/oracles/oracle-gaps/index.mjs and read the retention fixes from #61 plus the two probes, probe-gc.mjs and peak.mjs, to see what is already measured. Reproduce with the SAMPLE_FILE run at seed 20261112 and contexts 2, then take a late heap snapshot near 700 MB and walk the retainer path for the 217-to-821 MB growth that #61's counters do not cover. Done means the growth is attributed to a named structure, not that it is fixed; check whether it tracks klona's per-file working set rather than residue.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Summary
On the klona four-file suite (295 mutants, 2 contexts, seed 20261112), the gap CLI's child heap still grows during a run, after the retention fixes in #61. Heap after a forced GC, sampled every 2 s in the check child, went from about 87 MB at the start to about 217 MB in the middle and about 821 MB near the end. The run passes at a 1024 MB cap (child peak 930 MB) and completes at 1536 MB (child peak 985 MB). Main (before #61) fails at 2048 MB with a heap-limit fatal.
The growth is not attributed. The retention counters that #61 checks (Vitest's filesMap, pathsSet, idMap, the Vite copy nodes, the cold store, the stale context totals) stay at zero after each batch, so the remaining growth is in something those counters do not measure.
Measurement
Commit: 2b7efe6 on fix/gap-cli-retention (#61). Probe: the heap sampler preload (--expose-gc, forced GC every 2 s, main thread of the check child only).
# heap after GC, first / middle / last samples
cd <checkout of 2b7efe6>/packages/oracles/oracle-gaps
SAMPLE_FILE=/tmp/heap.jsonl node --expose-gc --import ./probe-gc.mjs ./index.mjs \
--package <klona> --source src/index.js,src/lite.js,src/full.js,src/json.js \
--seed 20261112 --contexts 2 --mutants <mutants dir> --out <out>
# child peak heap, no probe, cap at 1024 and 1536 MB
node --max-old-space-size=1024 --import ./peak.mjs ./index.mjs <same args>
node --max-old-space-size=1536 --import ./peak.mjs ./index.mjs <same args>
probe-gc.mjs samples process.memoryUsage().heapUsed after globalThis.gc() every 2 s, in the child only (ORACLE_GAPS_GROUP set). peak.mjs samples v8.getHeapStatistics().used_heap_size every 250 ms and prints the peak at exit.
Numbers, from the local runs against 67f057d/59363c8 code:
- heap after GC: 87 MB (first sample), 217 MB (middle), 821 MB (last sample before exit);
- 1024 MB cap: exit 0, child peak 930 MB;
- 1536 MB cap: exit 0, child peak 985 MB;
- default 2048 MB heap on
main(affeb1a): heap-limit fatal,done error ... ran out of memory.
What is ruled out
- Vitest state entries of retired copies (
filesMap,pathsSet,idMap): 0 after each batch. - Vite module nodes of retired copies: 0 after each batch.
- Vite nodes of non-copy files: at most one per file (the query-stripped check in #61).
- The cold run's store (
memoryStore): keeps nothing. - Vite's transform text, measured as a size on
ce6c93d: flat.
What is not known
- Which structure holds the second-half growth (from 217 to 821 MB). A late heap snapshot, taken near 700 MB, is the next step; its retainer path is not yet checked.
- Whether the growth follows klona's per-file working set (later files have more mutants and larger tests) rather than residue.
Limits
This issue is about measured heap growth, not a claimed leak. The measurements are from one suite on one machine, under varying load.
- Lenguaje dominante
- JavaScript
- Estrellas
- 5
- Forks
- 1
- Merge medio
- 8 h 31 min
- PR fusionados (30 d)
- 60
Preparar el entorno
Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de TanStack/oracles
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 62/100
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 64/100
Los mantenedores suelen responder en 1 día
-
Dificultad 5/5 Más de una semana Aptitud para principiantes 25/100
Los mantenedores suelen responder en 1 día
-
Dificultad 5/5 Más de una semana Aptitud para principiantes 35/100
Los mantenedores suelen responder en 1 día
Todos los issues de TanStack/oracles
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
Los mantenedores suelen responder en 1 día
-
Edit: Telemante [YT]Abiertochannels:edit check:passed
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
Los mantenedores suelen responder en 1 día
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 84/100
swc-project/swc-next-issues#490 ·
-
[workshop-sim] Improve: Add predict-and-check practice and checkpoint to Step 4 Actions introAbiertofeedback simulation workshop
Dificultad 2/5 1-3 horas Aptitud para principiantes 69/100
githubnext/gh-aw-workshop#5826 ·
Los mantenedores suelen responder en 1 día