ChatGPT desktop crashes when opening a long local Codex thread
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.4k
- PR merge metrics
- PR metrics pending
Description
Summary
The ChatGPT desktop app on macOS quits immediately when opening one specific long local Codex thread from the sidebar.
Steps to reproduce
- Launch the ChatGPT desktop app.
- Open an existing local Codex thread containing a long history with many tool/reasoning events and multiple spreadsheet preview images.
- The entire desktop app quits immediately.
Expected behavior
The selected thread opens normally.
Actual behavior
The ChatGPT desktop process crashes. Other threads open normally, and the affected thread still exists with an idle status.
Reproducibility
The crash occurs every time the affected thread is clicked.
Environment
- ChatGPT app: 26.831.21537 (build 7579)
- Bundled Codex Desktop: 0.152.1
- macOS: 15.3 (24D2059), arm64
- Crash time: 2026-09-10 01:21:22 +0800
Crash details
The macOS crash report shows EXC_BREAKPOINT / SIGTRAP on the main CrBrowserMain thread, with Chromium/V8 frames. This suggests the crash occurs while loading, rendering, or serializing the large thread.
Additional notes
- A newly created lightweight replacement thread opens normally.
- The affected thread contains many historical tool events and rendered spreadsheet previews.
- No private thread transcript or spreadsheet data is attached. A sanitized crash report can be provided if requested.
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 crash with the affected long local Codex thread and inspect the sanitized macOS crash report, especially the CrBrowserMain Chromium/V8 frames. Trace whether loading, rendering, or serializing the thread triggers the failure; done means the affected thread opens normally without crashing while lightweight and other threads continue to work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- macos, rust
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100