pingdotgg / pingdotgg/t3code

[Bug]: React #185 renderer crash recurs in ProviderModelPicker chunk on Alpha 0.0.40

Open
#11,308 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
23k
Forks
5.9k
Avg merge
11h 14m
Merged PRs (30d)
357

Description

Before submitting
  • I searched existing issues and did not find an open duplicate.
  • I included the available details needed to investigate the crash.
Area

apps/desktop

Steps to reproduce
  1. Use the T3 Code Alpha desktop app version 0.0.40.
  2. Open or use an existing thread.
  3. The renderer can crash to the T3 Code crash screen.

The exact interaction immediately preceding the crash was not captured, so this is not yet a deterministic reproduction. The environment/thread path from the crash screen is intentionally omitted because it contains private identifiers.

Expected behavior

The thread should remain usable and the desktop renderer should not crash.

Actual behavior

The renderer crashes with React error #185 (Maximum update depth exceeded). The later frames are in the ProviderModelPicker production chunk, though the minified stack alone does not prove that component is the root cause.

This may be a recurrence or a distinct path related to #9481. Its fix in #9482 is included in v0.0.40.

Impact

Major degradation or frequent failure

Version or commit

T3 Code (Alpha) 0.0.40

Environment

T3 Code desktop app. OS and provider/model were not captured.

Logs or stack traces
Error: Minified React error #185; visit https://react.dev/errors/185 for the full message or use the non-minified dev environment for full errors and additional helpful warnings.
    at fi (t3code://app/assets/dist-BLQyjWCD.js:26:27465)
    at ui (t3code://app/assets/dist-BLQyjWCD.js:26:27038)
    at Ko (t3code://app/assets/dist-BLQyjWCD.js:26:52159)
    at t3code://app/assets/dist-BLQyjWCD.js:26:52040
    at q (t3code://app/assets/ProviderModelPicker-D3YD1yeT.js:1:4228)
    at Qt (t3code://app/assets/ProviderModelPicker-D3YD1yeT.js:1:17170)
    at $t (t3code://app/assets/ProviderModelPicker-D3YD1yeT.js:1:17278)
    at pa (t3code://app/assets/ProviderModelPicker-D3YD1yeT.js:1:71935)
    at fa (t3code://app/assets/ProviderModelPicker-D3YD1yeT.js:1:70594)
    at da (t3code://app/assets/ProviderModelPicker-D3YD1yeT.js:1:69832)
Screenshots, recordings, or supporting files

None. No private logs or screenshots are attached.

Workaround

Unknown.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start in apps/desktop and trace the source corresponding to the ProviderModelPicker production chunk. Reproduce the crash in a non-minified development environment, then compare the behavior and fix described in #9481 and #9482. Done means the thread remains usable without React error #185 or a renderer crash.

Written by the indexing model from the issue text.

Assessment

Tech stack
react, typescript
Domain
desktop, frontend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.