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

UI freezes/deadlocks while debugging apps with many short-lived threads: Debug tree refresh (TreeModelContentProvider.updateNodes) collides with hover

Abierto
  • ¿Algo no está bien?
#4,403 2 comentarios 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
java
Área
desktop, developer-experience

Línea de trabajo

Start by tracing TreeModelContentProvider.updateNodes and the TreeViewer.replace/setChildCount calls named in the report, then compare them with the Text Viewer Hover Presenter Display.syncExec() path. Reproduce with thread start/death events during an active debug session and inspect the attached monitoring samples and .metadata/.log. Done means the repeated UI freezes or deadlock pair no longer occurs during refresh and hover.

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

Descripción

Environment: Eclipse 2026-09 (4.41.0.20260903-0719), Windows Server 2025,
JDK 27; debuggee is Spring Boot 4.1 with virtual threads (enabled by
default), sustained thread churn (scheduled tasks suffice — no external
traffic required).

Symptom: repeated UI freezes (2-30s+, cyclic, CPU only 1-3% during freeze).
Captured deadlock pair in .metadata/.log (2026-09-17/18):

main: TreeModelContentProvider.updateNodes (recursive x3)
-> TreeViewer.replace/setChildCount -> OS.SendMessage (SWT tree surgery)
'Text Viewer Hover Presenter': Display.syncExec() cancelled waiting for the
UI lock

Still reproducible on 4.41 as of 2026-09-24 (monitoring sample attached).

Triggered by thread start/death events while a debug session is active,
even when the user is not interacting.

Workarounds (verified): uncheck Show Running Threads / Thread Groups /
Virtual Threads / Monitors in the Debug view menu, or close the Debug view,
or run without the debugger.

Related:

  • eclipse-jdt/eclipse.jdt.debug#602 (virtual threads 1000x slower under
    the debugger)
  • eclipse-jdt/eclipse.jdt.debug#296 (virtual thread presentation in Debug
    view — same component)
  • eclipse-jdt/eclipse.jdt.debug#351 (same component, same stack shape:
    TreeModelContentProvider.handleAdd; closed as not planned)

Note: this issue is against the Debug view implementation
(org.eclipse.debug.ui, TreeModelContentProvider); the jdt.debug tickets
above are referenced as the same-family history in the debugger area.

Attached: raw monitoring samples (deadlock pair 2026-09-17, recurrence
2026-09-24).

Lenguaje dominante
Java
Estrellas
124
Forks
269
Merge medio
1 d 19 h
PR fusionados (30 d)
63

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 eclipse-platform/eclipse.platform.ui

Todos los issues de eclipse-platform/eclipse.platform.ui

Issues similares

Más issues de Java

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.