Android: a thread with many subagent rows takes 8–13 s to show its messages, and its forks inherit the delay
メンテナーはふだん 1 日以内に返信
まだ誰も着手していません。
評価
- 難易度
- 4/5
- 見積もり時間
- 3〜5日
- 初心者へのやさしさ
- 52/100
- issue の種類
- バグ
- 明瞭さ
- おおむね明確
- 活発さ
- 活発
- 技術スタック
- android, react-native, typescript
- 領域
- mobile, performance
調査の方向性
Start with apps/mobile/src/features/threads/thread-subagent-group.tsx at the reported subscription point, then trace how thread feed rows are rendered and whether full history or many subagent rows affect that path. Reproduce with the described Android thread and profile JavaScript rendering; compare against a thread with few subagent rows. Done means the messages appear promptly on repeated opens and forks, with profiling evidence identifying the delay.
索引モデルが issue の本文から書いたものです。
説明
What happened
On the Android app, one thread takes 8–13 seconds to show its messages each time I open it. The screen stays blank under the header until then. A fork of that thread has the same delay. Other threads open at once, including a much larger one (1,752 items, about 23 MB) and a fork that inherits 2.2 MB of history.
Diagnosis
- The server is not the cause. Each open sends
orchestration.subscribeThreadwith a resume sequence. The server replays in about 1 ms, and nogetThreadSnapshotWindowruns. All other RPCs in the window finished in under 15 ms. - The delay is in the app, between receiving the data and drawing the rows. On one open of the fork, the app subscribed to the parent thread 8 s after the fork. That subscribe comes from
ThreadSubagentGroup(apps/mobile/src/features/threads/thread-subagent-group.tsx:120), which mounts only when the feed draws a subagent group row. So no rows were mounted for 8 s. - The phone's
vcs.listRefscall came within 1 s of the content appearing on every open. It seems to follow the render; it does not cause the wait. - Settled state is not the cause. Unsettling the parent made no difference.
- Size alone is not the cause:
- Slow: 118 items, 1.1 MB, 24 subagent, 14 dynamic_tool, 23 command_execution, 2 compaction.
- Fast: 412 items, 2.2 MB, 2 subagent, 43 dynamic_tool, 117 command_execution.
- Fast: 1,752 items, 23 MB, 5 subagent. This one probably loads as a bounded window.
- Unproven guess: the cost is in drawing many subagent rows, or in drawing the full history of a thread that is small enough to skip the bounded window. A JS profile from the device would confirm it.
Steps to reproduce
- On desktop, use a thread with about 24 subagent items and some large dynamic tool results, small enough to load in full (about 120 items).
- Open it in the Android app 2.3.0 over T3 Connect. The messages appear after 8–13 s.
- Fork it at a later run and open the fork. It has the same delay.
- Open a thread with few subagent rows but more data. It opens at once.
I have no minimal repro yet. The steps above describe the thread I have.
Version
Android app 2.3.0 (Play Store); server 0.1.11-nightly.20261119.4941
Environment
Samsung SM-S928U1 (Android), connected through T3 Connect; server on macOS arm64
Evidence
# open fork (parent settled)
10:32:00.433 subscribeThread fork (resume, server work ~1 ms)
10:32:00.73-01.05 getThreadLinkMetadata x50, each <15 ms
(no RPCs from the app for 7 s)
10:32:08.519 subscribeThread parent <- subagent group row mounts; content visible
# open parent alone, unsettle, open fork, open parent again
11:46:19.891 subscribeThread parent
11:46:27.071 vcs.listRefs <- content visible (~8 s)
11:46:30.582 dispatchCommand thread.unsettle parent
11:46:37.301 subscribeThread fork
11:46:37.601 subscribeThread parent
11:46:48.021 vcs.listRefs <- content visible (~11 s)
11:46:51.901 subscribeThread parent
11:47:04.161 vcs.listRefs <- content visible (~12 s)
Related issues
#34240 "Mobile sync is slow" (closed, no details). That issue is about sync in general. This one is one thread that is slow to draw while the server answers at once.
Fix applied or workaround
None found. Nothing was changed on the machine. The parent was unsettled for the test and then settled again.
Filed by
Claude Code (Claude Opus 5.5, claude-opus-5-5) inside T3 Code, following the t3 triage playbook
- 主要言語
- TypeScript
- スター
- 24.8k
- フォーク
- 6.4k
- 平均マージ
- 4時間 29分
- マージ済み PR(30日)
- 488
環境構築
このプロジェクトの開発コンテナを、あなたの GitHub アカウントでブラウザ上に起動します。
- Dockerfile・Docker Compose ファイルなし
- プルリクエストのテンプレートあり
- コントリビューションガイドを読む
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- issue 番号を参照したプルリクエストを送ります。
pingdotgg/t3code のほかの issue
-
難易度 2/5 1〜3時間 初心者へのやさしさ 75/100
メンテナーはふだん 1 日以内に返信
-
needs more info
難易度 2/5 1〜3時間 初心者へのやさしさ 72/100
pingdotgg/t3code#39400 · コメント 1 件 ·
メンテナーはふだん 1 日以内に返信
-
[Bug]: Wrapped PR titles lose bottom padding in the thread details panel対応中かも @iamdatvt94 が 1 日前に担当しました。 オープンbug needs-triage
難易度 2/5 1〜3時間 初心者へのやさしさ 72/100
メンテナーはふだん 1 日以内に返信
-
bug needs-triage
難易度 2/5 1〜3時間 初心者へのやさしさ 66/100
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 73/100
メンテナーはふだん 1 日以内に返信
pingdotgg/t3code の issue をすべて見る
似ている issue
-
area:plugins kind:bug priority:p2 ready
難易度 2/5 1〜3時間 初心者へのやさしさ 90/100
メンテナーはふだん 1 日以内に返信
-
Escaped `*` followed by `*` (`\**`) never matches対応中かも @bardrop が今日担当しました。 オープン
難易度 2/5 1〜3時間 初心者へのやさしさ 71/100
editorconfig/editorconfig-core-js#172 ·
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 82/100
vega/vega-webgpu#40 ·
-
type: bug 🐛
難易度 2/5 1〜3時間 初心者へのやさしさ 63/100
puckeditor/puck#1929 ·
メンテナーはふだん 1 日以内に返信
-
compression() compresses every response at Brotli quality 11対応中かも @staylor が今日担当しました。 オープン
難易度 2/5 1〜3時間 初心者へのやさしさ 72/100
メンテナーはふだん 1 日以内に返信