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

Explicit gcTime schedules a GC timer during SSR, retaining the whole render in memory

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

I maintainer di solito rispondono entro 1 giorno

@AdzerKI ci sta già lavorando.

Dal 14/10/2026.

  • #12026 di @AdzerKI — aperta
  • #12053 di @mgarcialeniolabs — aperta
  • #12135 di @A-Raphie — aperta

Valutazione

Difficoltà
2/5
Tempo stimato
1-3 ore
Idoneità per principianti
25/100
Tipo di issue
Bug
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
node.js, react, typescript
Ambito
frontend

Direzione di ricerca

The bug is that an explicit finite gcTime schedules a real timer on the server, while the server default of Infinity does not. Start with the gist's gc-timer-retains-async-context.mjs reproduction and compare pending timers with default and finite. Pull request #12026 already targets this, so review it rather than starting a parallel fix. Done means no garbage-collection timer is scheduled on the server for any gcTime value.

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

Descrizione

Describe the bug

On the server, a query with an explicit finite gcTime (a regular client-side option) schedules a real setTimeout during SSR. The server default of Infinity is meant to prevent this, but an explicit gcTime bypasses it.

In Node, a pending timer keeps the render's async context (AsyncLocalStorage) alive until it fires. As a result, the entire render stays in memory: the HTML, the RSC payload, and the Request held by react-dom/server.

The timer serves no purpose. The request's QueryClient is discarded together with the response, so there is nothing left to garbage-collect.

Our case: Next.js 16, with a single useQuery({ gcTime: 24h }) in the root provider. Every render left behind a 24-hour timer and about 1.4 MB of retained memory. A heap snapshot of an idle replica showed 272 Request objects and 268 pending timers. Replicas grew until they hit the memory limit and were OOM-killed.

Your minimal, reproducible example

https://gist.github.com/AdzerKI/44081bf1d74a64d43ce651018ce2cba9

Steps to reproduce
  1. Save gc-timer-retains-async-context.mjs from the gist
  2. npm i @tanstack/query-core
  3. node --expose-gc gc-timer-retains-async-context.mjs default
  4. node --expose-gc gc-timer-retains-async-context.mjs finite
  5. Compare pendingTimers and rss in the output
Expected behavior

On the server, no garbage-collection timer should be scheduled for any gcTime value, the same as with the server default.

How often does this bug happen?

Every time

Screenshots or Videos

No response

Platform

OS: Linux
Runtime: Node.js 24.21.0 (server-side rendering, no browser involved)

Tanstack Query adapter

react-query

TanStack Query version

v5.104.2

TypeScript version

No response

Additional context

gcTime=default renders=2000 pendingTimers=0 external=2MB rss=119MB
gcTime=60000 renders=2000 pendingTimers=2000 external=1002MB rss=1069MB

Lingua principale
TypeScript
Stelle
50.4k
Fork
4.3k
Merge medio
11h 37m
PR unite (30g)
521

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 TanStack/query

Tutte le issue di TanStack/query

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.