Skip to content

Uningnored large data cause massive CPU bound by the worker that are created by Codex for git add and diffs #30477

Open

Description

@arkdong

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

26.623.42026

What subscription do you have?

Pro

What platform is your computer?

Darwin 25.5.0 arm64 arm

What issue are you seeing?

After a recent update, Codex Desktop repeatedly spawned multiple high-CPU git workers in one repo.

Observed commands:

  • git -c core.hooksPath=/dev/null -c core.fsmonitor= add -A
  • git -c core.hooksPath=/dev/null -c core.fsmonitor= add -- <hundreds of files>

Observed behavior:

  • 3-4 git processes at once, each around ~95-100% CPU
  • total CPU around 400-500%
  • commands were children of /Applications/Codex.app/Contents/MacOS/Codex
  • env included GIT_INDEX_FILE=/var/.../codex-index-*/index, so Codex was using temp indexes
  • however lsof showed git writing temp packs into the real repo .git/objects/pack/tmp_pack_*
  • logs showed requestKind=branch-diff-stats and turn-diff-capture-start
  • repo has a large unignored data/ directory: ~83GB, 372 files, 225 files >100MB

Codex should not spawn overlapping git add workers for the same repo, should avoid writing huge untracked blobs into the real object database just to compute diff stats, and should degrade/cap/skip large untracked files.

What steps can reproduce the bug?

Large unignored data like csv and txt

What is the expected behavior?

No response

Additional information

No response

Activity

  1. added
    appIssues related to the Codex desktop app
    on Jun 28, 2026
  2. github-actions commented on Jun 28, 2026

    @github-actions
    Contributor

    Potential duplicates detected. Please review them and close your issue if it is a duplicate.

    Powered by Codex Action

  3. awarnery commented on Sep 28, 2026

    @awarnery

    We are seeing similar behavior when using ChatGPT iOS Remote with a Linux Codex app-server: background workspace-diff refreshes repeatedly start overlapping Git workers even when the agent is no longer using tools.
    Large untracked generated caches make these workers CPU-intensive, and they can persist beyond the requested timeout before eventually finishing; the exact cause of the failed timeout or descendant cleanup has not been established.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    appIssues related to the Codex desktop appbugSomething isn't workingperformance

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions