[Bug]: Desktop backend dies with SIGTRAP in fff's background scan thread (realloc trap)
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
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:
- Run the desktop app on macOS (Apple Silicon) with several projects open and agents running.
- About an hour after launch, the bundled backend child was killed by
SIGTRAPthree 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
Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.
- Sin Dockerfile ni archivo de Docker Compose
- Tiene una plantilla de pull request
- Leer la guía de contribución
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 pingdotgg/t3code
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
Los mantenedores suelen responder en 1 día
-
needs more info
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
pingdotgg/t3code#39400 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
[Bug]: Wrapped PR titles lose bottom padding in the thread details panelPosiblemente ocupada @iamdatvt94 la tomó hace 1 día. Abiertobug needs-triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
Los mantenedores suelen responder en 1 día
-
bug needs-triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 66/100
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 73/100
Los mantenedores suelen responder en 1 día
Todos los issues de pingdotgg/t3code
Issues similares
-
area:plugins kind:bug priority:p2 ready
Dificultad 2/5 1-3 horas Aptitud para principiantes 90/100
Los mantenedores suelen responder en 1 día
-
Escaped `*` followed by `*` (`\**`) never matchesPosiblemente ocupada @bardrop la tomó hoy. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 71/100
editorconfig/editorconfig-core-js#172 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
vega/vega-webgpu#40 ·
-
Adjust break point sizingAbiertotype: bug 🐛
Dificultad 2/5 1-3 horas Aptitud para principiantes 63/100
puckeditor/puck#1929 ·
Los mantenedores suelen responder en 1 día
-
compression() compresses every response at Brotli quality 11Posiblemente ocupada @staylor la tomó hoy. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
Los mantenedores suelen responder en 1 día