Maximum update depth exceeded

[specialCoder]

Error Type

Runtime Error

Error Message

Maximum update depth exceeded. This can happen when a component repeatedly calls setState inside componentWillUpdate or componentDidUpdate. React limits the number of nested updates to prevent infinite loops.

at PreviewPane (src/components/preview-pane.tsx:283:15)
at Home (src/app/page.tsx:91:15)

Code Frame

  281 |                 produced html, and only on tabs that show the user that html. */}
  282 |             {(tab === "preview" || tab === "code") && status === "done" && html && (
> 283 |               <DeployControl />
      |               ^
  284 |             )}
  285 |             <StatusPill status={status} />
  286 |           </div>

Next.js version: 16.2.6 (Turbopack)

[lefarcen]

Superseded: this was briefly labeled for community help, but after checking related issues we found existing PR coverage for the same DeployControl loop. Please follow #33 / #37 instead.

[lefarcen]

Hi @specialCoder — thanks for the clear stack trace. The frame at PreviewPane line 283 is where <DeployControl /> mounts, and this looks like the same deploy-control render loop already tracked in #31 / #32.

The relevant source path is src/components/deploy-control.tsx: its Zustand selector currently falls back to selectActiveTask(s)?.deployments ?? [], which creates a fresh empty array for tasks with no deployment history and matches React/Zustand's infinite snapshot/update loop. PR #33 is the focused fix for that path, and #37 also contains the same stabilization as part of a larger history feature, so we'll keep this report linked while maintainers decide which implementation lands.

[lefarcen]

Quick update: PR #41 is now also open for this same DeployControl render loop. It applies the same core fix shape discussed here: replacing the fresh deployments ?? [] fallback with a stable shared empty deployments array so the Zustand selector stops returning a new snapshot each render.

There is already overlapping PR coverage in #33, so we'll track maintainer review across those PRs and keep this issue open until one fix lands.

[lefarcen]

Quick update: PR #33 has merged into main with the focused fix for this crash. The current src/components/deploy-control.tsx now uses a shared EMPTY_DEPLOYMENTS fallback instead of allocating deployments ?? [] on each selector run, which is the loop we matched from your PreviewPane / <DeployControl /> stack trace.

@specialCoder, when you have a chance, could you verify against the latest main or the next deployed build? If the error still appears, please drop the new stack trace here and we’ll reopen the investigation from that path.

[lefarcen]

Closing this now since PR #33 has landed and the fix is present on main under next/src/components/deploy-control.tsx: DeployControl now uses a stable EMPTY_DEPLOYMENTS fallback instead of allocating a fresh empty array for tasks with no deployment history.

If the maximum-update-depth error still appears on the latest build, please reopen or comment with the new stack trace and we’ll dig back in.