Codex app is continuously spawning git.exe processes

Open
#34,672 1 comment 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
git, rust
Domain
desktop, devtools

Research direction

Reproduce the behavior on Windows in a Subversion project directory using the provided reproduction steps and Feedback ID. Start by tracing the desktop app's repository detection and git process handling; done means no empty .git directory is created and no git.exe processes are spawned for that project.

Written by the indexing model from the issue text.

Description

app bug performance windows-os
What version of the Codex App are you using (From “About Codex” dialog)?

26.715.31925

What subscription do you have?

Enterprise

What platform is your computer?

Windows

What issue are you seeing?

I am using the ChatGPT Windows desktop app, and working on a project directory that uses Subversion. Every time I get the agent to modify some files, it creates an empty .git directory and then starts to continuously spawn git.exe processes in an infinite loop. I noticed that my CPU fans were active while my computer was doing nothing. It doesn't stop until I do rm -rf .git; taskkill /f /im git.exe.

To reproduce, working a Subversion repo in the project directory. Have Codex write some python code. Then have it modify some python code. Maybe then restart the app and ask it to modify some more code. You should start to see the behaviour described.

What steps can reproduce the bug?

Feedback ID: 019f4fcf-3371-7941-9cab-3c089744d809

What is the expected behavior?
  • Do NOT create empty .git directory
  • Do NOT start git.exe at all when the the .git directory is empty
Additional information

No response

Dominant language
Rust
Stars
125k
Forks
19.5k
Avg merge
1m
Merged PRs (30d)
1k

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.

More from openai/codex

All issues in openai/codex

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.