[Windows] Orphaned git.exe processes persist in 26.707.9981.0 and correlate with kernel pool growth

What version of the Codex App are you using (From “About Codex” dialog)?

26.707.9981.0

What subscription do you have?

ChatGPT Plus

What platform is your computer?

Microsoft Windows NT 10.0.26200.0 x64

What issue are you seeing?

The Windows Codex/ChatGPT desktop app repeatedly spawns local Git metadata commands even when I have not requested any Git operation.

Observed commands include:

• git status --porcelain
• git rev-parse HEAD
• git remote -v
• git config --null --get core.fsmonitor

I confirmed that a newly created git.exe process had the main ChatGPT.exe process as its direct parent. The short-lived parent/helper processes exit, but many git.exe processes remain alive for several minutes as orphaned processes.

During approximately two minutes of monitoring:

• The number of live git.exe processes increased from 31 to 36.
• Git processes consumed approximately 1.22 GB of private memory.
• Git processes held approximately 3,349 handles.
• Git working set was approximately 245 MB.
• Nonpaged pool increased from approximately 1.09 GB to 1.40 GB.
• Paged pool increased from approximately 856 MB to 894 MB.

The kernel pool growth is temporally correlated with the repeated Git/conhost process creation. I cannot attribute every byte of kernel pool growth to Git without pool-tag tracing, but the user-mode Git process and handle accumulation is directly observable.

No GitHub remote or authentication is configured for the active workspace. The observed commands are local metadata checks and should not require GitHub connectivity.

What steps can reproduce the bug?

Feedback ID: 019f6440-966a-76b1-8e36-1ab349c360d9

What is the expected behavior?

_No response_

Additional information

App package:

OpenAI.Codex_26.707.9981.0_x64__2p2nqsd0c76g0

Selected executable:

app\ChatGPT.exe

This appears closely related to the following issues, but it is still reproducible in the newer 26.707.9981.0 build and includes measured memory, handle, and kernel-pool growth:

• #17229 — repeated git.exe status and orphaned git.exe / conhost.exe
• #20933 — multiple Git processes triggered by opening a project/chat
• #22085 — sustained high resource usage from repeated Git for Windows processes
• #20867 — repeated Git metadata work in non-Git workspaces

The active workspace has no configured Git remote. GitHub authentication or remote connectivity should therefore not be required for reproduction.