React Query Devtools retains detached transition targets through bundled Kobalte registry
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
- 25/100
- Tipo di issue
- Bug
- Chiarezza
- Abbastanza chiara
- Stato di attività
- Attiva
- Stack tecnologico
- javascript, react
- Ambito
- frontend, performance
Direzione di ricerca
The retention is in the published Devtools bundle, where transitionsByElement and the bundled Kobalte utils 0.9.2 track transition targets on the body. Start from the linked repro's /react/ entry and window.repro.countAliveTargets() after a forced GC, then compare against the standalone Kobalte example. Done means the stopped-event run drops to 0 after GC without breaking active transitions on connected elements, which depends on the upstream Kobalte fix being released into Devtools.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
Describe the bug
React Query Devtools 5.107.1 embeds Kobalte's global transition tracking. If an application element stops a native transitionend event from bubbling and is removed after the transition completes, the bundled registry can retain the detached element. The body-level registry tracks application elements outside the Devtools UI too.
In a minimal React app with one stable query and the Devtools panel mounted, 1,000 completed and removed transition targets remain alive after manual Chrome garbage collection. In the normal-event control, 0 remain alive after GC.
The underlying Kobalte issue and proposed fix are:
This report tracks the downstream Devtools impact and eventual inclusion of the upstream fix. The tested published @tanstack/query-devtools bundle includes transitionsByElement and the affected utils 0.9.2 code. Updating an application's separate Kobalte dependency will not replace code already embedded in that bundle.
Your minimal, reproducible example
https://github.com/whatisyourname0/kobalte-transition-retention-repro/tree/e26a70a/react
The repository includes both a standalone Kobalte example at / and the React Query Devtools example at /react/. The React entry does not execute a direct Kobalte import or use a patched dependency. It mounts QueryClientProvider, one stable sample query, and ReactQueryDevtools with initialIsOpen: true.
Steps to reproduce
git clone https://github.com/whatisyourname0/kobalte-transition-retention-repro.git
cd kobalte-transition-retention-repro
git checkout e26a70a
npm ci
npm run dev
- Open
/react/on the displayed local origin. Wait until the Devtools panel andSample query readyappear. - Click Run stopped events. Wait for completion: 1,000 started, 1,000 ended, 1,000 removed, 0 cancelled. These are real CSS transitions; each target stops
transitionendpropagation, then is removed after completion. - Open Chrome DevTools → Memory → Collect garbage.
- Evaluate
window.repro.countAliveTargets()in Console: 1000. - Reload, wait for the panel, click Run control, wait for completion, and collect garbage again. The same expression returns 0.
- To inspect ownership, take a heap snapshot after the stopped case and inspect detached
retention-probetargets andtransitionsByElementin the Devtools bundle.
The fixture keeps only WeakRefs once the async run settles and never logs/exports individual targets. A count before GC is not evidence of retention. callbackRan: null on the React page is intentional: it does not import Kobalte's private callback helper. The standalone page separately demonstrates the blocked callback and Map retaining path.
Expected behavior
Removed application elements are released even when completion events do not reach the body-level listener. Active transitions on connected elements continue to be respected.
How often does this bug happen?
Reproduced in the stopped-event run; the normal-event control released all targets.
Screenshots or Videos
Reproduction UI (not a Memory-panel capture):

Platform
macOS 26.7; Chrome 157.0.8103.78.
Tanstack Query adapter
react-query
TanStack Query version
@tanstack/react-query and @tanstack/react-query-devtools: 5.107.1. React / React DOM: 19.3.1. Exact dependencies are locked. Node >=24 to run the fixture.
TypeScript version
Not applicable; the reproduction uses JavaScript.
Additional context
Both React-page cases completed all 1,000 native transitions and removed all targets with no cancellation events. The affected transition has already ended before removal, so removal cannot be expected to emit transitioncancel for it.
The Kobalte-only reproduction has also been compared against the proposed upstream fix (1,000 retained → 0 after GC). The React Devtools reproduction uses the unmodified published Devtools bundle; that candidate comparison has not been repeated against a rebuilt Devtools bundle. This report concerns the demonstrated DOM retention condition, not a claim that Query cache retention or all application memory growth has this cause.
Could you track incorporating the Kobalte fix into a Devtools release once upstream review/release is complete, or advise on a suitable interim mitigation?
- Lingua principale
- TypeScript
- Stelle
- 50.6k
- Fork
- 4.2k
- Merge medio
- 8h 37m
- PR unite (30g)
- 450
Preparare l'ambiente
- 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 TanStack/query
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
TanStack/query#12466 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
solid-query: STRICT_READ_UNTRACKED on Solid 2 — client()/options() read in component body (useMutation, useBaseQuery)Forse di nuovo libera @LeonxLJX l’ha presa 74 giorni fa e non c’è nessuna pull request aperta. Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 84/100
TanStack/query#11358 · 2 commenti · 1 reazione ·
I maintainer di solito rispondono entro 1 giorno
-
Infinite render loop when select maps keepPreviousData to undefined in v5.105.2+Forse già presa @mooxl l’ha presa 6 giorni fa. Aperta
Difficoltà 3/5 1-2 giorni Idoneità per principianti 35/100
TanStack/query#12574 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
infiniteQuery throws "getNextPageParam is not a function" when 2+ stale pages are cachedForse già presa @abu-tahir-0 l’ha presa 7 giorni fa. Aperta
Difficoltà 3/5 1-2 giorni Idoneità per principianti 42/100
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 5/5 Più di una settimana Idoneità per principianti 25/100
I maintainer di solito rispondono entro 1 giorno
Tutte le issue di TanStack/query
Issue simili
-
Type/Improvement
Difficoltà 2/5 1-3 ore Idoneità per principianti 67/100
OpenNSW/nsw-srilanka#1259 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
oxc-project/tsrs#1010 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
Fission-AI/OpenSpec#2260 ·
I maintainer di solito rispondono entro 1 giorno
-
Add: ESP 1 UKApertacheck:passed streams:add
Difficoltà 1/5 1-3 ore Idoneità per principianti 64/100
I maintainer di solito rispondono entro 1 giorno
-
area:infra area:storage bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 76/100
THU-MAIC/OpenMAIC#2311 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno