Skip to content

Windows: memory usage spikes and Codex freezes after repeated context compactions #24095

Open

Description

@Herrtian

Summary

On Windows, Codex can become unresponsive after a long-running thread has gone through multiple automatic context compactions. Memory usage then climbs quickly and can exhaust available RAM.

Environment

  • Platform: Windows
  • App: Codex Desktop
  • Version: not captured yet

Steps to reproduce

  1. Start a long-running thread in Codex Desktop on Windows.
  2. Continue working until automatic context compaction runs several times.
  3. Keep using the same thread after each compaction.
  4. Watch Codex memory usage in Task Manager.

Actual behavior

  • After several compactions, the UI can freeze or stop responding.
  • Codex memory usage rises rapidly.
  • The machine can get close to running out of memory.
  • Recovery usually requires killing or restarting Codex, and the same thread may remain difficult to use.

Expected behavior

Codex should stay responsive after repeated context compactions. Memory used by old thread state should be released or bounded instead of growing until the app or system becomes unusable.

Notes

This looks related to #14472 and #19381, but the trigger here is repeated context compaction in the same long-running Windows session, followed by rapid memory exhaustion.

Activity

  1. added
    bugSomething isn't working
    appIssues related to the Codex desktop app
    windows-osIssues related to Codex on Windows systems
    contextIssues related to context management (including compaction)
    on May 22, 2026
  2. github-actions commented on May 22, 2026

    @github-actions
    Contributor
  3. Herrtian commented on May 22, 2026

    @Herrtian
    Author

    I reviewed the duplicate suggestions and related reports.

    The remaining useful distinction seems to be the exact lag/freeze shape:

    1. opening/selecting an existing large thread freezes,
    2. sending a new prompt in an already-open thread freezes,
    3. memory spikes right after or during context compaction,
    4. Electron main process crashes with RangeError: Invalid string length,
    5. renderer crashes on Markdown/directive parsing.

    This report is meant to track case 3 on Windows: repeated compactions in one long-running session, followed by rapid memory growth and UI freeze. I will leave it open for now and try to capture the app version plus whether the spike starts before or after the compacted checkpoint is written.

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 workingcontextIssues related to context management (including compaction)performancewindows-osIssues related to Codex on Windows systems

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions