Codex Desktop Crashes While Idle as Computer Use Workers Multiply
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)?
Version: 26.810.52044, build 6662
What subscription do you have?
ChatGPT Pro 20x
What platform is your computer?
Hardware: Mac mini M4, 16 GB macOS: 15.7.8 (24G824)
What issue are you seeing?
Reproduction: launch application and leave idle; Computer Use instances multiply; crash after approximately five minutes
Activity Monitor: more than 20 Computer Use processes visible
Faulting thread: 315 computer-use
Immediate failure: node::OOMErrorHandler
Dispatch warning: soft limit of 64 blocked synchronous dispatch threads
Incident ID: 2390B917-4DEC-4128-B322-F6540B47B9CA
What steps can reproduce the bug?
Reproduction: launch application and leave idle; Computer Use instances multiply; crash after approximately five minutes
What is the expected behavior?
Codex should launch normally and remain stable while idle. It should create only the Computer Use workers required for active tasks, reuse or terminate them correctly, and prevent their number from continually increasing. Memory and thread usage should remain stable, the application should stay responsive, and it should not crash when no task is running.
Additional information
This is consistently reproducible after restarting the Mac, even when Codex is the only application running and no task is active. Within several minutes, Activity Monitor shows more than 20 Computer Use instances, memory usage increases, and the application crashes.
Environment:
Mac mini M4 with 16 GB RAM
macOS 15.7.8 (24G824)
ChatGPT/Codex version 26.810.52044, build 6662
Bundle identifier: com.openai.codex
The crash report identifies the faulting thread as computer-use, with SIGABRT, node::OOMErrorHandler, and the message: Dispatch Thread Soft Limit Reached: 64 (too many dispatch threads blocked in synchronous operations).
In the attached incident, the application launched at approximately 18:11:43 and crashed at 18:17:16 while idle. This appears to indicate that Computer Use workers are repeatedly being created or restored without being terminated correctly. I have attached the full crash report and Activity Monitor evidence.
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 by reproducing the idle launch on macOS and review the attached crash report alongside Activity Monitor. Confirm why Computer Use workers multiply while no task is active; done means worker count, memory, and thread usage remain stable and Codex stays running while idle.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- macos, node.js
- Domain
- desktop, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100