[Fiber] Fix hang when updating a dehydrated boundary inside a hidden tree (#37135)

Closes https://github.com/vercel/next.js/issues/95848.

Fixes a hang: if an update changes what's inside a server-rendered
Suspense or Activity boundary before that boundary has hydrated, and the
affected content is hidden, React stops committing. The new content
renders once its data arrives, but the render is discarded every time,
nothing is scheduled, and nothing ever pings — the update never lands
and the app appears frozen.

"Hidden" means either of two things, and there's a test for each:

- the update itself hides a dehydrated `<Activity>` (while mounting new
sibling content that suspends), or
- the dehydrated boundary is inside the primary tree of a parent
boundary that just suspended and is showing its fallback.

This is how we found it in practice.

With https://github.com/vercel/next.js/pull/95682, pressing Back before
hydration finishes made the router replay the missed navigation from its
first effect. This worked fine outside of Cache Components, but in Cache
Components mode (which turns on Activity), the old page's Activity
(still dehydrated) gets hidden, the new page's content suspends inside
the layout's Suspense boundary, and after the data arrives the page
stays blank forever.

As a result, https://github.com/vercel/next.js/pull/95682 got reverted.
If we fix this, we can unrevert it.

## Why it happens

When an update changes a dehydrated boundary, we schedule a render at a
higher priority to hydrate it before the update applies. If we already
tried that, we give up and client render, but mark the render as
suspended so it doesn't commit while the hydration attempt might still
finish first.

Both steps assume the attempt can actually run. Inside a hidden tree it
can't, because updates in hidden trees are deferred until the tree is
revealed. The scheduled attempt never runs but still consumes the retry
lane, which sends every later render into the give-up path — and the
give-up path keeps discarding finished renders, waiting for a hydration
attempt that isn't in flight. Once the last piece of data resolves
there's nothing left to ping us awake. The root ends up with
`pendingLanes === suspendedLanes`, `pingedLanes` empty, and no callback
scheduled.

The update doesn't need to be sync or discrete: a plain setState from an
effect is enough. Wrapping the same update in `startTransition` avoids
it, which is probably why this went unnoticed.

## The fix

If the boundary is inside a hidden tree (`isCurrentTreeHidden()`), skip
the hydration attempt and client render right away. There's nothing
visible to protect: replacing hidden server HTML doesn't show, and the
replacement children render when the tree is revealed.

One behavior note: this discards the hidden server HTML instead of
preserving it for later hydration on reveal, same as the existing
give-up path. Keeping it dehydrated and hydrating at reveal would be a
nicer follow-up, but needs commit-phase support that doesn't exist
today.

## How did you test this change?

The first commit adds failing tests for both boundary types; the fix
makes them pass. `startTransition` variants of the same scenarios are
included as passing controls. Ran the Activity, partial/selective
hydration, Fizz, Suspense, and Offscreen suites in both release
channels.
This commit is contained in:
dan
2026-07-28 23:18:44 +01:00
committed by GitHub
parent d77b0baa1d
commit fb1b84f747
3 changed files with 284 additions and 0 deletions
@@ -4300,4 +4300,136 @@ describe('ReactDOMServerPartialHydration', () => {
root.unmount();
expect(container.innerHTML).toEqual('<!--&--><!--/&-->');
});
it('recovers when an update changes a dehydrated boundary inside a suspended parent boundary', async () => {
let suspend = false;
let resolve;
const promise = new Promise(resolvePromise => (resolve = resolvePromise));
function Sibling() {
if (suspend) {
throw promise;
}
return <span id="sibling">Sibling</span>;
}
function App({showSiblingOnMount}) {
const [showSibling, setShowSibling] = React.useState(false);
React.useEffect(() => {
if (showSiblingOnMount) {
// Not a transition: this update reaches the dehydrated inner
// boundary at default priority, before it has hydrated.
setShowSibling(true);
}
}, [showSiblingOnMount]);
return (
<div>
<Suspense fallback={null}>
{showSibling ? <Sibling /> : null}
<Suspense fallback={null}>
<span id="content">{showSibling ? 'b' : 'a'}</span>
</Suspense>
</Suspense>
</div>
);
}
// Don't suspend on the server.
suspend = false;
const finalHTML = ReactDOMServer.renderToString(
<App showSiblingOnMount={false} />,
);
const container = document.createElement('div');
container.innerHTML = finalHTML;
expect(container.textContent).toBe('a');
// Hydrate. The first effect mounts a suspending sibling in the outer
// boundary (so the outer boundary shows its fallback and its primary
// content is hidden), and at the same time changes the input of the
// inner boundary, which is still dehydrated.
suspend = true;
await act(() => {
ReactDOMClient.hydrateRoot(container, <App showSiblingOnMount={true} />);
});
// The sibling's data arrives.
suspend = false;
await act(async () => {
resolve();
await promise;
});
// The outer boundary should reveal both the sibling and the updated
// inner content.
const sibling = container.querySelector('#sibling');
const content = container.querySelector('#content');
expect(sibling).not.toBe(null);
expect(sibling.style.display).not.toBe('none');
expect(content).not.toBe(null);
expect(content.style.display).not.toBe('none');
expect(content.textContent).toBe('b');
});
it('recovers when a transition changes a dehydrated boundary inside a suspended parent boundary', async () => {
// Same as the previous test, except the update is wrapped
// in startTransition.
let suspend = false;
let resolve;
const promise = new Promise(resolvePromise => (resolve = resolvePromise));
function Sibling() {
if (suspend) {
throw promise;
}
return <span id="sibling">Sibling</span>;
}
function App({showSiblingOnMount}) {
const [showSibling, setShowSibling] = React.useState(false);
React.useEffect(() => {
if (showSiblingOnMount) {
React.startTransition(() => {
setShowSibling(true);
});
}
}, [showSiblingOnMount]);
return (
<div>
<Suspense fallback={null}>
{showSibling ? <Sibling /> : null}
<Suspense fallback={null}>
<span id="content">{showSibling ? 'b' : 'a'}</span>
</Suspense>
</Suspense>
</div>
);
}
suspend = false;
const finalHTML = ReactDOMServer.renderToString(
<App showSiblingOnMount={false} />,
);
const container = document.createElement('div');
container.innerHTML = finalHTML;
expect(container.textContent).toBe('a');
suspend = true;
await act(() => {
ReactDOMClient.hydrateRoot(container, <App showSiblingOnMount={true} />);
});
suspend = false;
await act(async () => {
resolve();
await promise;
});
const sibling = container.querySelector('#sibling');
const content = container.querySelector('#content');
expect(sibling).not.toBe(null);
expect(sibling.style.display).not.toBe('none');
expect(content).not.toBe(null);
expect(content.style.display).not.toBe('none');
expect(content.textContent).toBe('b');
});
});
@@ -2976,4 +2976,129 @@ describe('ReactDOMServerPartialHydrationActivity', () => {
'<div>1</div><span>client</span><div>2</div>',
);
});
it('commits new suspending content next to a dehydrated Activity that hides', async () => {
let suspend = false;
let resolve;
const promise = new Promise(resolvePromise => (resolve = resolvePromise));
function Second() {
if (suspend) {
throw promise;
}
return <span id="second">Second</span>;
}
function App({showSecondOnMount}) {
const [active, setActive] = React.useState('first');
React.useEffect(() => {
if (showSecondOnMount) {
// Not a transition: this update reaches the dehydrated Activity at
// default priority, before it has hydrated.
setActive('second');
}
}, [showSecondOnMount]);
return (
<div>
<Suspense fallback={null}>
{active === 'second' ? <Second /> : null}
<Activity mode={active === 'first' ? 'visible' : 'hidden'}>
<span id="first">First</span>
</Activity>
</Suspense>
</div>
);
}
// Don't suspend on the server.
suspend = false;
const finalHTML = ReactDOMServer.renderToString(
<App showSecondOnMount={false} />,
);
const container = document.createElement('div');
container.innerHTML = finalHTML;
expect(container.textContent).toBe('First');
// Hydrate. The first effect mounts new content (still loading) and hides
// the server-rendered Activity while its subtree is still dehydrated.
suspend = true;
await act(() => {
ReactDOMClient.hydrateRoot(container, <App showSecondOnMount={true} />);
});
// The data for the new row arrives.
suspend = false;
await act(async () => {
resolve();
await promise;
});
// The new row should be visible and the old row hidden.
const second = container.querySelector('#second');
const first = container.querySelector('#first');
expect(second).not.toBe(null);
expect(second.style.display).not.toBe('none');
expect(first === null || first.style.display === 'none').toBe(true);
});
it('commits new suspending content next to a dehydrated Activity that hides (transition)', async () => {
// Same as the previous test, except the update is wrapped
// in startTransition.
let suspend = false;
let resolve;
const promise = new Promise(resolvePromise => (resolve = resolvePromise));
function Second() {
if (suspend) {
throw promise;
}
return <span id="second">Second</span>;
}
function App({showSecondOnMount}) {
const [active, setActive] = React.useState('first');
React.useEffect(() => {
if (showSecondOnMount) {
React.startTransition(() => {
setActive('second');
});
}
}, [showSecondOnMount]);
return (
<div>
<Suspense fallback={null}>
{active === 'second' ? <Second /> : null}
<Activity mode={active === 'first' ? 'visible' : 'hidden'}>
<span id="first">First</span>
</Activity>
</Suspense>
</div>
);
}
suspend = false;
const finalHTML = ReactDOMServer.renderToString(
<App showSecondOnMount={false} />,
);
const container = document.createElement('div');
container.innerHTML = finalHTML;
expect(container.textContent).toBe('First');
suspend = true;
await act(() => {
ReactDOMClient.hydrateRoot(container, <App showSecondOnMount={true} />);
});
suspend = false;
await act(async () => {
resolve();
await promise;
});
const second = container.querySelector('#second');
const first = container.querySelector('#first');
expect(second).not.toBe(null);
expect(second.style.display).not.toBe('none');
expect(first === null || first.style.display === 'none').toBe(true);
});
});
+27
View File
@@ -204,6 +204,7 @@ import {
import {
pushHiddenContext,
reuseHiddenContextOnStack,
isCurrentTreeHidden,
} from './ReactFiberHiddenContext';
import {findFirstSuspended} from './ReactFiberSuspenseComponent';
import {
@@ -1019,6 +1020,19 @@ function updateDehydratedActivityComponent(
if (didReceiveUpdate || hasContextChanged) {
// This boundary has changed since the first render. This means that we are now unable to
// hydrate it. We might still be able to hydrate it using a higher priority lane.
if (isCurrentTreeHidden()) {
// This boundary is inside a hidden subtree, where all work is
// deferred until the tree is revealed. Selective hydration works by
// rendering the boundary at a higher priority before the update
// applies, so it can't make progress here; delaying the commit to
// wait for it would deadlock. Replacing hidden content isn't
// visible, so give up and client render.
return retryActivityComponentWithoutHydrating(
current,
workInProgress,
renderLanes,
);
}
const root = getWorkInProgressRoot();
if (root !== null) {
const attemptHydrationAtLane = getBumpedLaneForHydration(
@@ -3028,6 +3042,19 @@ function updateDehydratedSuspenseComponent(
if (didReceiveUpdate || hasContextChanged) {
// This boundary has changed since the first render. This means that we are now unable to
// hydrate it. We might still be able to hydrate it using a higher priority lane.
if (isCurrentTreeHidden()) {
// This boundary is inside a hidden subtree, where all work is
// deferred until the tree is revealed. Selective hydration works by
// rendering the boundary at a higher priority before the update
// applies, so it can't make progress here; delaying the commit to
// wait for it would deadlock. Replacing hidden content isn't
// visible, so give up and client render.
return retrySuspenseComponentWithoutHydrating(
current,
workInProgress,
renderLanes,
);
}
const root = getWorkInProgressRoot();
if (root !== null) {
const attemptHydrationAtLane = getBumpedLaneForHydration(