openai / openai/codex

Windows desktop browser process crashes while generating a very large Git review diff

Open
#44,690 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

app bug code-review performance windows-os
Dominant language
Rust
Stars
125k
Forks
19.4k
PR merge metrics
PR metrics pending

Description

Summary

Codex Desktop on Windows repeatedly terminated while its automatic Git review/turn-diff processing handled an unusually large staged diff. Crashpad classified every retained crash as an Electron browser-process crash.

This may share underlying symptoms with #41268 and appears related to the Git review/output-pressure reports in #35776 and #30820, but this report isolates a reproducible workload characteristic: very large generated diff output.

Environment
  • Windows 11 x64
  • Codex Desktop Microsoft Store package: 26.903.8094.0
  • ChatGPT.exe / Chromium: 152.0.7977.83
Observed behavior
  • The complete desktop app crashed five times within roughly 20 minutes.
  • Each retained Crashpad sidecar reported capture_kind=crash, ptype=browser, and osarch=x86_64.
  • Desktop logs ended abruptly without a fatal JavaScript exception.
  • Windows had no matching Application Error/WER event.
Workload immediately preceding the crashes
  • The workspace had roughly 264,000 staged added lines.
  • Eight generated NDJSON files were approximately 33.5 MB each.
  • Codex's automatic review-summary / turn-diff Git processing captured approximately 101 MB of git diff output.

The timing and repeated browser-process classification suggest output volume or memory pressure in the automatic review path. This is a correlation, not a confirmed native root cause.

Local containment

Adding the following rule made Git treat the generated records as non-diffable and prevented their bodies from entering Codex's review diff:

*.ndjson -diff

I have not reproduced the crash since applying that containment yet, so I am not claiming it as a confirmed fix.

Expected behavior

Automatic Git review/status processing should cap or stream large output and fail gracefully. A large staged diff should not terminate the Electron browser/main process or the full desktop application.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the review-summary/turn-diff Git path with the described large staged NDJSON workload, then inspect the Crashpad browser-process reports and abrupt desktop logs. Done means automatic Git review/status processing handles large output without terminating the Electron browser or desktop app, either through bounded output or graceful failure.

Written by the indexing model from the issue text.

Assessment

Tech stack
electron, git, rust
Domain
desktop, tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.