A native program crashes with SIGSEGV when a string or JSON builder grows past 4 MiB

Abierto
#3,642 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

@alantriesagain ya está trabajando en esto.

Desde el 14/11/2026.

  • #3643 de @alantriesagain — abierto

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
22/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
c, linux, typescript

Línea de trabajo

Start in scr_sa_run_move in scr_alloc.c, where the run is moved with mremap(..., MREMAP_MAYMOVE | MREMAP_FIXED, q) and the fallback memcpy(q, p, have) runs after a failed call. Reproduce with the 1760 x 2400-character JSON snippet from the issue, which should exit 139 today. Done means that snippet prints 4229281 and the slice without crashing, and that the fallback no longer writes to unmapped memory. PR #3643 already targets this, so review or coordinate there before starting a second fix.

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

Descripción

A compiled program dies with SIGSEGV when a string builder grows past 4 MiB, in scr_sa_run_move's fallback copy. Node runs the same program.

Environment

  • scriptc 0.4.12 from npm (the release's @scriptc/compiler under Node, linking @scriptc/runtime-linux-x64-gnu); upstream main at 3198190fb3 has the same code.
  • Linux 6.8.0 x86_64, glibc 2.39.

What happens

const lines: string[] = [];
for (let i = 0; i < 1760; i++) lines.push("x".repeat(2400));
const text = JSON.stringify(lines);
console.log(String(text.length));
console.log(text.slice(0, 8));

Node prints 4229281 and ["xxxxxx. The native build prints nothing and exits 139.

The backtrace from an unstripped build of a larger app that hit it (resuming a 5 MB transcript, which became one JSON text):

#0  __memcpy_evex_unaligned_erms
#1  scr_sa_run_move () at scr_alloc.c
#2  scr_mem_realloc_ref ()
#3  scr_str_regrow ()
#4  scr_jb_grow ()
#5  scr_jb_put_json_str ()
#6  scr_dyn_json_write ()
...
#9  scr_json_stringify_with ()

At the fault: p=0x387c00000, q=0x388400000, have=0x800000, n=0x800019. info proc mappings showed an unmapped hole at exactly [0x388400000, 0x388c00000), which is q to q + have.

Cause

scr_sa_run_move moves the run with mremap(p, have, have, MREMAP_MAYMOVE | MREMAP_FIXED, q). When the old run spans two mappings, the call fails. On Linux a failed MREMAP_FIXED has already unmapped the destination range, so the fallback memcpy(q, p, have) writes into unmapped memory.

#3595 (the native CLI segfaulting on a large program) may be the same crash, since the CLI builds large strings too. I have not checked that.

Lenguaje dominante
TypeScript
Estrellas
6.6k
Forks
216
Merge medio
9 h 35 min
PR fusionados (30 d)
775

Preparar el entorno

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 vercel-labs/scriptc

Todos los issues de vercel-labs/scriptc

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.