macOS app crashes after 1–2 minutes while idle in RemoteHostedPIPContentService
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.818.31338 (6892)
What subscription do you have?
ChatGPT Business
What platform is your computer?
Darwin 25.5.0 arm64 arm
What issue are you seeing?
The ChatGPT/Codex macOS app consistently crashes approximately one to two minutes after opening, even when the app is idle and I have not performed any actions.
The macOS crash report shows:
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Subtype: KERN_INVALID_ADDRESS, possible pointer authentication failure
Termination Reason: Namespace SIGNAL, Code 11, Segmentation fault: 11
Triggered Thread: 7
Dispatch Thread Soft Limit Reached: 64 (too many dispatch threads blocked in synchronous operations)
The crashed thread contains RemoteHostedPIPContentService, sky.node, AECreateAppleEvent, and NSAppleEventDescriptor. Several additional threads appear blocked while RemoteHostedPIPContentService attempts to send bootstrap AppleEvents.
System:
2021 14-inch MacBook Pro
Apple M1 Max
64 GB RAM
macOS Tahoe 26.5.2 (25F84)
ChatGPT/Codex version 26.818.31338 (6892)
Bundle identifier: com.openai.codex
What steps can reproduce the bug?
- Launch the ChatGPT/Codex macOS application.
- Leave the application open without interacting with it.
- Wait approximately one to two minutes.
- The application closes unexpectedly and macOS generates a crash report.
The crash happens consistently.
Troubleshooting already completed:
- Force-quit and restarted the Mac
- Uninstalled and reinstalled the application
- Reset AppleEvents, Screen Recording, Camera, and Microphone permissions using tccutil
- Removed the application's retained local support, cache, preference, saved-state, WebKit, and HTTP storage data
- Restarted the Mac and tested with freshly generated application data
The crash continues after all of these steps.
What is the expected behavior?
The application should remain open and stable while idle and should not launch repeated background picture-in-picture service operations that exhaust the dispatch-thread limit.
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 by reproducing the idle crash on the listed macOS and app versions, then inspect the RemoteHostedPIPContentService and sky.node paths named in the crash report. Pay particular attention to the AECreateAppleEvent and NSAppleEventDescriptor activity and the blocked dispatch threads. Done means the app remains open while idle without repeated background operations or dispatch-thread exhaustion.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- macos, rust
- Domain
- desktop, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100