Computer Use repeatedly triggers sustained CUA process load and causes severe Mac overheating
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.4k
- PR merge metrics
- PR metrics pending
Description
What version of the Codex App are you using (From “About Codex” dialog)?
26.810.52044
What subscription do you have?
PRO 5X
What platform is your computer?
macOS 26.5.2(25F84)
What issue are you seeing?
标题:Computer Use 可重复触发 CUA 进程持续高负载并导致 Mac 严重过热
设备环境:
- MacBook Air(Mac17,3)
- Apple M5,10 核 CPU
- 16 GB 内存
- macOS 26.5.2(25F84)
- Codex 26.810.52044
问题描述:
实际使用 Computer Use 后,可重复出现 Mac 剧烈发热。异常进程为 ChatGPT/Codex 内置的 cua_node/.../kernel.js,两次观察到其持续占用约 152%–260% CPU、约 2 GB 内存,峰值约 4.9 GB,并可残留运行数小时(分别约 3 小时和 19 小时)。
进程采样显示它在反复进行文件读取、字符串转换及 V8 垃圾回收,并持续读取一个约 830 MB 的 Codex rollout 会话日志。SkyComputerUseService 本身几乎不占 CPU,主要问题集中在 CUA Node 内核。
禁用 Computer Use 开关不会终止已经运行的异常 CUA 进程,必须手动结束 kernel.js 及其 node_repl 父进程后,CPU 和内存才立即恢复正常。重启后仅打开开关不会异常,但实际调用 Computer Use 后会再次复现。
期望行为:
- Computer Use 操作结束、取消或超时后,CUA 内核应及时退出并释放资源。
- 禁用 Computer Use 时应终止已有会话和后台进程。
- 不应无界、反复全量读取大型 rollout 日志。
- 建议增加空闲超时、CPU/内存 watchdog、增量日志读取和明确的 Force Stop 按钮。
该问题具有明确的可重复性,并会导致设备持续过热、性能下降和额外耗电。
What steps can reproduce the bug?
Feedback ID: 01a03424-6a2e-7e51-a41c-ddd1e3562aaa
What is the expected behavior?
No response
Additional information
No response
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
Start with the CUA kernel.js process and its interaction with SkyComputerUseService; reproduce Computer Use using feedback ID 01a03424-6a2e-7e51-a41c-ddd1e3562aaa and inspect the repeated reads of the large rollout log. Done means Computer Use cancellation, timeout, completion, or disabling stops the existing CUA processes and releases CPU and memory without sustained load.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, macos, node.js
- Domain
- desktop, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100