Maximum update depth exceeded Error

[Echoidf]

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 |
| ^
284 | )}
285 |
286 |

Next.js version: 16.2.6 (Turbopack)

[lefarcen]

Hi @Echoidf — thanks for filing the follow-up stack trace. This looks like the same DeployControl selector loop as #31, just surfacing one frame higher through PreviewPane at the <DeployControl /> render.

The likely trigger is src/components/deploy-control.tsx using selectActiveTask(s)?.deployments ?? []; when there are no deployments yet, that fallback creates a fresh array snapshot each render, which can trip React/Zustand into the maximum-update-depth path. PR #25 is already open with the small fix to reuse a stable empty deployments array, so we’ll track the implementation/review there and keep this issue linked to that work.

[lefarcen]

Hi @Echoidf — PR #33 is now open and appears to target the same DeployControl render loop behind this preview-pane crash. The patch stabilizes the deployments selector fallback for tasks with no prior deploys, so <DeployControl /> should stop producing a new snapshot on each render.

We'll track the implementation/review in #33 and keep this issue open until the fix lands.

[lefarcen]

Quick update: PR #37 is now also open and includes the same DeployControl empty-deployments selector stabilization relevant to this crash, alongside a larger per-task history feature.

There is already a focused fix in #33 for this exact loop, so we’ll keep the issue open while maintainers decide which implementation path lands and until the fix is merged.

[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]

Hi @Echoidf — the focused fix for this has now landed in PR #33.

What changed: DeployControl now reuses a module-level EMPTY_DEPLOYMENTS fallback instead of creating a fresh [] from the Zustand selector when a task has no prior deployments. That should stop the repeated snapshot updates that were surfacing as the maximum-update-depth crash in PreviewPane.

Could you try the latest build when you get a chance and confirm whether the preview opens cleanly for a fresh task? We'll keep this issue open for your validation.

[lefarcen]

Closing this now since PR #33 has landed and the fix is present on main: DeployControl now uses a stable EMPTY_DEPLOYMENTS fallback instead of allocating a fresh empty array for tasks with no prior deployments.

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