useDeferredValue with an object created during render hangs the page after any re-render (0.3.0) #153
Send to my agentSummary#
Passing an object created during render to useDeferredValue hangs the tab as soon as the component re-renders after mount. React settles after 3 renders. Redact renders forever and keeps throwing from the flushPending guard, so the main thread stays busy and the page stops responding.
React's docs warn that this pattern causes an unnecessary background render. It is wasteful there, but it finishes.
Reproduction#
No router, Suspense, compiler or hydration is involved.
import { useDeferredValue, useEffect, useState } from 'react'
import { createRoot } from 'react-dom/client'
window.renders = 0
function App() {
window.renders++
const [, setTick] = useState(0)
useDeferredValue({})
useEffect(() => setTick(1), [])
return <p>done</p>
}
createRoot(document.getElementById('root')).render(<App />)
Build with vite build with and without the redact() plugin, then open the page.
| Runtime | Renders after about 3 s | Page errors | Page |
|---|---|---|---|
| React 19.3.1 | 3 | 0 | Responsive |
| Redact 0.3.0 | 3,873,811 | 44,178 | Unresponsive |
These are unminified production builds, so the errors are the bare Error() from flushPending. The count is what had accumulated when I paused the page in the debugger.
The first render does not loop. It takes any re-render after mount, and in my tests a setState in an effect, a setState in a layout effect and a useSyncExternalStore update all triggered it.
Possible cause#
This comes from reading the source. I have not tested a patch.
In v() in packages/redact/src/dom/transitions.ts, a normal render whose value differs from hook.s calls enqueue(fiber), which also calls scheduleUpdate(fiber). flushRoot then runs renderUpdates followed by flushTransitions. The transition pass accepts the value, but the fiber still seems to be queued for a normal pass. That pass creates another new object, which differs from hook.s, so it enqueues again.
Real-world impact#
I hit this in a TanStack Start app where a hook returned a new query options object on every render, with a stable query key, and the result went to useDeferredValue. The page froze on load under Redact and works under React.
Memoizing the value avoids the loop.
Environment#
@tanstack/redact0.3.0 (also 0.2.5), defaultredact()preset- React 19.3.1 (control)
- Vite 7.3.7,
@vitejs/plugin-react5.2.0 - Chromium 156 (Playwright), Node 26
Sign in to join this conversation.
I have a fix for this on my fork, since I couldn't open a PR here: https://github.com/Tarekkharsa/redact/commit/f7e69c68be41f7fcf12b603491c3d79b7554638e
The queued commit effect in
enqueue()now schedules an update only while the fiber is still inroot.tr. It includes regression tests and a changeset. Tests and type checks pass, and a TanStack Start app that froze on this bug now passes its specs for that page.pnpm size:checkis 1 byte over the default Vite budget (23,447 vs 23,446), and I didn't change the allowance, so that needs your decision.