Hacktoberfest 2026:維護者為十月標記出來的 issue,仍然開放、適合新手。 瀏覽 Hacktoberfest issue

[Bug]: Conversation feed stutters and bounces back while streaming (macOS, arm64 desktop)

未關閉
#146 0 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

還沒有人認領這個 Issue。

評估

難度
4/5
預估耗時
3-5 天
新手友好度
15/100
Issue 類型
缺陷
描述清晰度
基本清楚
活躍度
活躍
技術堆疊
electron, macos

研究方向

The payload names no repository files, so start by locating where the desktop app launches its Chromium helper processes and where the --disable-features list is set; check whether DropInputEventsWhilePaintHolding is disabled there. Then find the feed component that auto-follows new streamed content and see how it handles user scroll. Done means a reproducible streaming-scroll test or a documented root cause, plus a fix that keeps scroll position while output streams.

由索引模型根據 Issue 內容生成。

描述

Summary

While a response is streaming, the conversation feed scrolls with heavy stutter / dropped frames, and scrolling up with the mouse bounces back to the newest content — so long streamed outputs can't be read in real time. Idle scrolling is fine; this only happens while tokens are arriving.

Environment

  • Command Code desktop 0.1.54 (auto-updated from 0.1.53 while testing — not fixed in 0.1.54)
  • macOS 27.0 (build 26A428)
  • Apple M1 (8-core); built-in Retina display 4480 x 2520 at native scaling, single display
  • App is native arm64 (Mach-O thin (arm64); sysctl.proc_translated = 0)
  • GPU acceleration on — helper runs as Command Code Helper --type=gpu-process

Steps to reproduce

  1. Open a session with a large transcript (observed around 3 MB / ~500 entries).
  2. Send a prompt that produces a long streamed response.
  3. While tokens are still arriving, scroll up with the mouse/trackpad.

Result: the feed stutters and snaps back to the bottom; earlier lines can't be read.

Expected

  • Scrolling stays smooth while streaming.
  • Scrolling up detaches from the auto-follow instead of bouncing back.

What was ruled out

  • Rosetta / translation — app is native arm64. It was previously running the Intel build; switching to the Apple-Silicon build did not fix this streaming scroll stutter.
  • Software rendering — GPU process is present and GPU-compositing flags are active on the renderer.
  • Non-native display scaling — display is at its native mode.
  • A settings workaround — the config registry exposes no scroll / auto-follow / transcript-render option.
  • A newer version — 0.1.54 is current.

Likely suspect

Helpers are launched with --disable-features=...,DropInputEventsWhilePaintHolding,.... With that feature disabled, input events aren't shed while a paint is held, so scroll input queues during heavy streaming repaint — which matches the reported "scroll up and it bounces back" behavior.

Requests

  • Add a scroll-follow toggle, or detach auto-follow as soon as the user scrolls up.
  • Consider disabling elastic overscroll for the feed (overscroll-behavior: none).
  • Consider re-enabling DropInputEventsWhilePaintHolding.
  • Investigate repaint/relayout cost for large transcripts while streaming.

Diagnostics

  • During streaming the renderer is the hot process; on the pre-arm64 (Intel) build the main process spiked to ~100% CPU.
  • No crash reports for the app; the ~/.commandcode data directory is small (no obvious leak).
  • Trace ids (for support): 99e8f6007c859816e280fac896c81bad, d0da42a640d1a24a1b6d1a1c7dcb2588
主要語言
Shell
星號
96
分支
7
平均合併
2 小時 46 分鐘
30 天內合併 PR
1

環境準備

這個專案沒有提供開發容器、Dockerfile 或貢獻指南,環境需要你自己搭建:先看它的 README,通用步驟見我們的新手貢獻指南。

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

CommandCodeAI/desktop 的其他 Issue

查看 CommandCodeAI/desktop 的全部 Issue

相似的 Issue

更多 Shell/Bash Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。