Some git related commands lead to a git.exe crash window showing up on Windows
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)?
latest
What subscription do you have?
Plus
What platform is your computer?
Windows 11
What issue are you seeing?
A git.exe error window appears (at first seemingly out of nowhere).
It says something like the instruction 0x000000.... pointed to RAM at 0x0000000000000000, the read procedure could not be executed in RAM, click OK to end the program, click cancel to debug the program.
(roughly, not exact transcription of that window).
What steps can reproduce the bug?
This is actually reproducible. Whenever Codex does something with git rebase (I think continue, ..., a bit more complicated command), then this happens. Not entirely sure why, and possibly hard to prevent. But wanted to report.
What is the expected behavior?
No response
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 issue on Windows 11 during the Codex flow that runs a git rebase-related command, especially rebase continuation or a more complex rebase command. Inspect which git.exe invocation triggers the crash window and compare it with simpler git operations. Done means the reproducible flow no longer opens a git.exe crash dialog.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git
- Domain
- cli, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100