[Bug] 桌面版切换「闲时任务」面板后返回主会话卡顿,Renderer/GPU 进程持续高 CPU
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 22
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
提交前确认 · Pre-submission checklist
- 我已搜索过现有 issue,确认这不是重复 / I searched existing issues and confirmed this isn't a duplicate.
- 我已阅读 CONTRIBUTING.md / I've read CONTRIBUTING.md.
问题类别 · Category
性能 · Performance
涉及的 Agent 框架 · Agent framework
ZCode Agent(自研)
严重程度 · Severity
影响体验 · Major (功能可用但体验受损 / works but degraded)
复现频率 · Reproducibility
必现 · Always
问题描述 · Description
在桌面版点击左侧「闲时任务」区,再点回主会话界面,UI 卡顿数秒无响应。
实测(活动监视器):ZCode Helper (Renderer) 进程 CPU 持续 25–28%、GPU 进程约 25%,静置后仍不回落。
已删除全部会话后逐个点入仍卡顿,可排除会话数据量因素。
已排除其他因素:仅挂载 1 个定时任务且处于暂停状态(runCount=0);本地 MCP(gbrain HTTP 127.0.0.1:3131)响应 1–3ms;系统内存空闲 64%。
怀疑为前端渲染层问题。另注:启动参数含 --disable-features=MacWebContentsOcclusion(窗口遮挡不暂停渲染),供参考。
复现步骤 · Steps to reproduce
- 打开 ZCode 桌面版 v3.10.1(macOS)
- 点击左侧边栏「闲时任务」区
- 再点回主会话/任务界面
- 界面卡顿数秒;期间活动监视器显示 ZCode Helper (Renderer) CPU 约 25–28%、GPU 进程约 25%
- 删除全部会话后重复 1–4,仍必现卡顿
期望表现 · Expected behavior
切换面板应即时响应;空闲状态下渲染进程 CPU 应接近 0%。
实际表现 · Actual behavior
切回主界面后 UI 卡顿数秒;渲染进程 CPU 长时间维持 25% 以上不回落;删除全部会话后依旧。
ZCode 版本 · ZCode version
3.10.1 (3.10.1.6272)
设备 / 系统 / 浏览器 · Device / OS / Browser
MacBook(Apple Silicon)/ macOS(darwin 25.6.0)/ ZCode 桌面版(Electron)
截图 / 录屏 / 日志 · Screenshots / Recordings / Logs
top 采样:Renderer(pid) CPU 28.5%/24.4%/27.6%(三次独立采样),GPU 进程 24.9%。
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the issue in ZCode desktop v3.10.1 on macOS by switching from the idle-tasks panel back to the main session. Start with renderer and GPU profiling around that transition, using the reported CPU measurements and the --disable-features=MacWebContentsOcclusion argument as context. Done means the switch responds promptly and renderer/GPU CPU usage returns near idle after the UI settles.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- electron
- Domain
- desktop, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100