Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

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

Aperta
  • Qualcosa non va?
#4,403 2 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
45/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
java
Ambito
desktop, developer-experience

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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).

Lingua principale
Java
Stelle
124
Fork
269
Merge medio
2g 3h
PR unite (30g)
69

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di eclipse-platform/eclipse.platform.ui

Tutte le issue di eclipse-platform/eclipse.platform.ui

Issue simili

Altre issue su Java

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.