macOS app crashes after 1–2 minutes while idle in RemoteHostedPIPContentService

Open 💬 1 comment Opened Aug 21, 2026 by JasperT18
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

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?

  1. Launch the ChatGPT/Codex macOS application.
  2. Leave the application open without interacting with it.
  3. Wait approximately one to two minutes.
  4. 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_

View original on GitHub ↗

1 Comment

github-actions[bot] contributor · 6 days ago

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

  • #38515
  • #38744
  • #39403
  • #39151

Powered by Codex Action