# fix\(desktop\): a primary backend crash loop now shows why it can't start · pingdotgg/t3code

[View on GitCafe](https://git.cafe/pingdotgg/t3code/commit/ad92ed834bb363f1f3d9ff898396e704a7939d1a)

Repository: [pingdotgg/t3code](https://git.cafe/pingdotgg/t3code)

Visibility: public

Requested revision: ad92ed834bb363f1f3d9ff898396e704a7939d1a

Requested commit: ad92ed834bb363f1f3d9ff898396e704a7939d1a

Commit: ad92ed834bb363f1f3d9ff898396e704a7939d1a

Tree: 1e103717cd3262a74b890d7069356a81e31b7b0a

Author: Julius Marminge

Committer: Julius Marminge

## Message

```
fix(desktop): a primary backend crash loop now shows why it can't start

The primary backend could exit before readiness on every restart (for example
with a corrupt statev2.sqlite) and the user saw no window and no error, because
the renderer is served by that backend.

After three consecutive exits without readiness, the pool now shows a native
error box with the exit reason and the server-child.log path. Restarts keep
going in the background, and the streak resets once the backend becomes ready.

Closes #10517

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

```

## Parents

- [62b39618fddb20d1a6384dee34d4774b745b3506](https://git.cafe/pingdotgg/t3code/commit/62b39618fddb20d1a6384dee34d4774b745b3506?format=markdown)

[Source at this commit](https://git.cafe/pingdotgg/t3code/tree/ad92ed834bb363f1f3d9ff898396e704a7939d1a?format=markdown)