Scrolling a long thread stutters after loading earlier turns (timeline measure pass and per-scroll message re-derivation)
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
- Specificata chiaramente
- Stato di attività
- Attiva
- Stack tecnologico
- react, typescript
- Ambito
- frontend, performance
Direzione di ricerca
Start by locating useTimelineFollow and the legend-list measure pass identified in the CPU trace (W$ in the generated bundle); the issue gives no source file paths, so search the repository for those entry points. Profile scrolling after repeatedly loading earlier turns and inspect the layout effects and row derivation they trigger. Done means the long-thread scroll no longer repeatedly measures every mounted container or rebuilds unchanged message rows, with the initial-page behavior preserved.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
What happened
Scrolling the chat timeline of a long thread (about 3,250 items, 318 turns) stutters on the Windows desktop app. The jank appears after "Load earlier turns" has been used. At the initial page the same thread scrolls smoothly.
Diagnosis
Repro in the web client served by the thread's own server, headless Chromium at 1600x1000, with a scripted 8 s rAF scroll sweep on .messages-timeline-scroll:
| State | Scroll height | DOM nodes | p50 | p99 | Max frame | Frames >50 ms |
|---|---|---|---|---|---|---|
| Initial page | 3,812 px | 2,053 | 16.7 ms | 17.2 ms | 67 ms | 1 |
| After 8x "Load earlier turns" | ~197,000 px | ~3,000 | 16.7 ms | 83 ms | 200 ms | 9 |
The DOM stays near 3,000 nodes because the list is virtualized, so the cost scales with the amount of loaded history rather than with the DOM.
The CPU trace for the loaded state (8 s of scrolling) shows:
- 14,980 forced style and layout flushes totalling 1.13 s, plus 640 ms of self time in
getBoundingClientRect. All of it comes from the legend-list measure pass (r0->W$in main-*.js), which runs from layout effects during commits and measures every mounted container. InW$,getBoundingClientRectis followed byoffsetWidth/offsetHeightand sometimesgetComputedStyle. - Scroll-time work in useTimelineFollow-*.js that rebuilds message rows:
formatMessagetakes 218 ms,encodeabout 116 ms, andlt/Q/ytin session-logic run underLp/gh/Dh. This re-derivation runs while scrolling, even though the thread is idle and nothing new is arriving. - Long Animation Frame attribution names
DOMWebSocket.onmessageas the entry point for most long frames (2.45 s), because the runtime picks up work queued behind socket messages. The handler itself takes under 20 ms; the cost is the rendering work above.
Rendering itself is small: about 300 ms in the render phase and 190 ms in paint.
Caveat: headless Chromium rasterizes in software, so absolute frame times are higher than in the desktop app. The layout and JS costs above are CPU-side and carry over.
Steps to reproduce
- Open a thread with a few thousand timeline items.
- Click "Load earlier turns" until a few hundred thousand px of history is loaded.
- Scroll up and down with the wheel or trackpad.
Version
Desktop app 0.1.11-nightly.20261119.4954 (Windows). The thread lives on a linked Linux environment that runs 0.1.11-nightly.20261119.4941, and the headless repro used that server's web client.
Environment
Windows 11 Pro 26300, Ryzen 7 5800X, 128 GB RAM, RTX 3080 Ti, 60 Hz. The machine was idle during the repro (no process above about one core of 16, GPU 3D under 4%).
Evidence
Local scroll traces, LoAF summaries and the CPU trace are available on request.
Workaround
Switch away from the thread and back; it reopens at the first page, which scrolls smoothly.
Related
- #13925: the same symptom on the Android app, which has a separate native feed. That report says web and desktop are smooth, which no longer holds once older turns are loaded.
- #12689: Windows desktop renderer stalls from synchronous topology IPC. This repro ran in a browser with no
desktopBridge, so that path is excluded here and may add to it on desktop. This desktop'sdesktop.trace.ndjsonshows 4,111sendSynccalls in 8.3 h, with handlers at a 1.6 ms maximum. - #37639: a forced layout from equations when a thread opens; a different trigger.
- #22350: iOS LegendList
scrollBycorrections; this one is about scroll position, not CPU.
Agent: Claude Code (Opus 5.5), following the t3 triage playbook.
- Lingua principale
- TypeScript
- Stelle
- 24.8k
- Fork
- 6.4k
- Merge medio
- 4h 29m
- PR unite (30g)
- 488
Preparare l'ambiente
Avvia il container di sviluppo del progetto nel browser, con il tuo account GitHub.
- Nessun Dockerfile né file Docker Compose
- Ha un modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di pingdotgg/t3code
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 75/100
I maintainer di solito rispondono entro 1 giorno
-
needs more info
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
pingdotgg/t3code#39400 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
[Bug]: Wrapped PR titles lose bottom padding in the thread details panelForse già presa @iamdatvt94 l’ha presa 1 giorno fa. Apertabug needs-triage
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
I maintainer di solito rispondono entro 1 giorno
-
bug needs-triage
Difficoltà 2/5 1-3 ore Idoneità per principianti 66/100
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 73/100
I maintainer di solito rispondono entro 1 giorno
Tutte le issue di pingdotgg/t3code
Issue simili
-
area:plugins kind:bug priority:p2 ready
Difficoltà 2/5 1-3 ore Idoneità per principianti 90/100
I maintainer di solito rispondono entro 1 giorno
-
Escaped `*` followed by `*` (`\**`) never matchesForse già presa @bardrop l’ha presa oggi. Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 71/100
editorconfig/editorconfig-core-js#172 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 82/100
vega/vega-webgpu#40 ·
-
Adjust break point sizingApertatype: bug 🐛
Difficoltà 2/5 1-3 ore Idoneità per principianti 63/100
puckeditor/puck#1929 ·
I maintainer di solito rispondono entro 1 giorno
-
compression() compresses every response at Brotli quality 11Forse già presa @staylor l’ha presa oggi. Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
I maintainer di solito rispondono entro 1 giorno