[Bug]: Desktop backend dies with SIGTRAP in fff's background scan thread (realloc trap)

Abierto
#38,975 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
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
45/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
electron, typescript
Área
backend, desktop

Línea de trabajo

Start in the apps/server area named in the report and trace how workspace file search uses @ff-labs/fff-node and its native @ff-labs/fff-bin-darwin-arm64 binding during directory scans. The crash reports point to realloc on an fff background scan thread, but there is no deterministic repro or specific source file or test named. Investigate the native allocation or binding behavior and define a reproducible test that confirms indexing no longer crashes the backend.

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

Descripción

Before submitting
  • I searched existing issues and did not find a duplicate.
  • I included enough detail to reproduce or investigate the problem.
Area

apps/server

Steps to reproduce

No deterministic repro yet. What happened:

  1. Run the desktop app on macOS (Apple Silicon) with several projects open and agents running.
  2. About an hour after launch, the bundled backend child was killed by SIGTRAP three times in six minutes (23:53, 23:54 and 23:59 local). Each time the app restarted it within a second.

All three crash reports have the same shape: the faulting thread is one of @ff-labs/fff's own threads (fff-bg-2, fff-bg-6, and an unnamed fff scan thread), inside realloc, while other fff threads are still listing directories (getattrlistbulk). The JavaScript main thread is in ordinary V8 code each time; nothing is calling finder.destroy() at that moment.

Expected behavior

File search indexing never takes the backend down.

Actual behavior

The backend process dies with EXC_BREAKPOINT (SIGTRAP). macOS shows " quit unexpectedly" while the window stays up, and any agent turn running at that moment is cut off; providers resume in a fresh native session.

The trap is raised by Electron's allocator from a realloc that libfff_c.dylib makes on its own background thread, so it looks like heap damage inside fff (or its Node binding) that Electron's allocator catches. Because the backend runs inside the Electron binary (ELECTRON_RUN_AS_NODE), malloc/realloc go through Electron's allocator, which may be why this shows up on desktop.

Impact

Major degradation or frequent failure

Version or commit

0.1.10 (main as of 2026-11-18). This is an internal build of T3 Code with the desktop app renamed. apps/server/src/workspace has only upstream commits (it lacks #38337 and #38585, which do not touch native memory), and @ff-labs/fff-node / @ff-labs/fff-bin-darwin-arm64 are 0.11.0, the same as main.

Environment

macOS 26.6.2, arm64, desktop app, Electron 44.10.1, @ff-labs/fff-node 0.11.0

Logs or stack traces
# desktop log (server-child.log)
backend child process failure output end  details="pid=2198 killed by SIGTRAP"   05:53:33Z
backend child process failure output end  details="pid=21068 killed by SIGTRAP"  05:54:22Z
backend child process failure output end  details="pid=27689 killed by SIGTRAP"  05:59:12Z

# crash report (.ips), process = the backend child, parent = the app
exception: EXC_BREAKPOINT (SIGTRAP), codes 0x1, 0x...3c4
termination: Trace/BPT trap: 5

# faulting thread fff-bg-6 (same in the other two reports)
0-4  Electron Framework   (allocator trap; symbols resolve to unrelated names)
5    Electron Framework
6    Electron Framework
7    libsystem_malloc.dylib  _malloc_zone_realloc
8    libsystem_malloc.dylib  _realloc
9-23 libfff_c.dylib          (no symbols)
24   libsystem_pthread.dylib _pthread_start

# other threads at the same moment
fff-bg-0..8   libfff_c.dylib, waiting on a condition variable (except the faulting one)
4-7 threads   libsystem_kernel getattrlistbulk < libfff_c.dylib   (directory scan in progress)
main thread   Electron Framework / V8 only, no fff or ffi-rs frames
Workaround

None found. The backend restarts by itself, but running agent turns are interrupted each time.

Lenguaje dominante
TypeScript
Estrellas
24.8k
Forks
6.4k
Merge medio
4 h 29 min
PR fusionados (30 d)
488

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 pingdotgg/t3code

Todos los issues de pingdotgg/t3code

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.