Chrome renderer freeze when TanStack row model gates a Suspense child

Clone la reproducción independiente enlazada, ejecute pnpm install, pnpm check y pnpm preview:repro, y luego reproduzca el congelamiento en Chrome con el Synchronous active row button. Empiece con el ejemplo reducido de App y compare el comportamiento con y sin table.getRowModel().rows.length; se considera completado cuando se haya establecido si el problema pertenece a TanStack Table o a la interacción entre React y el navegador, y se haya documentado una corrección confirmada o una transferencia con el alcance delimitado.

Summary

In a Vite production preview, Chrome can freeze after a real browser click when all of the following happen in the same render path:

1. A synchronous React state update switches TanStack Table from empty data to a fresh one-row data array.
2. The component reads table.getRowModel().rows.length.
3. That row-model read gates mounting a child inside Suspense.
4. The child suspends by throwing a timer-backed promise.

The repro is standalone and uses only local React state/data.

Reproduction

Standalone repro:

https://github.com/HaukeSchnau/trusted-click-table-suspense-freeze-repro

Repro commit used while filing this issue:

https://github.com/HaukeSchnau/trusted-click-table-suspense-freeze-repro/tree/67c0ea8

git clone https://github.com/HaukeSchnau/trusted-click-table-suspense-freeze-repro.git
cd trusted-click-table-suspense-freeze-repro
pnpm install
pnpm check
pnpm preview:repro

Then open http://127.0.0.1:4174/ in Chrome and click Synchronous active row.

The repro command uses Vite production preview. I have not characterized Vite dev mode.

Expected behavior

The click completes, the Suspense fallback handles the thrown promise, and the page remains responsive.

Actual behavior

The Chrome tab freezes during the click. Reloading or closing the tab is required to recover.

Environment

• React 19.2.3
• react-dom 19.2.3
• @tanstack/react-table 8.21.3
• Vite 7.3.0
• TypeScript 5.9.3
• Node v24.11.1
• pnpm 10.25.0
• Chrome 147.0.0.0 from navigator.userAgent
• macOS 26.4.1 (25E253)

I have only confirmed the freeze in Chrome. Firefox and Safari are untested.

Reduced trigger

const columns: [] = [];
const coreRowModel = getCoreRowModel();
let resolved = false;
let promise: Promise<void> | undefined;

function Suspender() {
  if (!resolved) {
    promise ??= new Promise((resolve) => {
      window.setTimeout(() => {
        resolved = true;
        resolve();
      });
    });

    throw promise;
  }

  return null;
}

function App() {
  const [active, setActive] = useState(false);
  const table = useReactTable({
    data: active ? [null] : [],
    columns,
    getCoreRowModel: coreRowModel,
  });

  return (
    <>
      {table.getRowModel().rows.length ? (
        <Suspense fallback={null}>
          <Suspender />
        </Suspense>
      ) : null}

      <button id="sync-active" onClick={() => setActive(true)}>
        Synchronous active row
      </button>
    </>
  );
}

Isolation notes

The repro does not use TanStack Router, TanStack Query, React Compiler, Vite React plugin, APIs, auth, or production app code.

This may ultimately be a React Suspense or browser interaction. I’m filing here first because the smallest library-specific condition I’ve isolated is the TanStack Table row-model read over fresh data; the reduced app becomes responsive when that row-model read is removed.