Memory leak

Open 💬 5 comments Opened Jun 23, 2026 by uuuus

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

Version 26.616.71553 • Released 23 cze 2026

What subscription do you have?

plus

What platform is your computer?

Microsoft Windows NT 10.0.19045.0 x64

What issue are you seeing?

Subject: Windows memory issue after Codex repo analysis - very high Page Table / system memory growth

I’m seeing a reproducible Windows memory issue related to Codex desktop after repository analysis.

Environment:

  • Windows 11
  • 32 GB RAM
  • Codex desktop app
  • F-Secure installed
  • Local repo analyzed: Novera

Observed behavior:

  1. After reboot, baseline memory usage is low/normal.
  2. Launching Codex alone causes only a small increase.
  3. Running a broad repository analysis in Codex increases memory usage significantly.
  4. Excluding the repo folder from F-Secure reduced the worst spikes, so antivirus scanning was clearly part of the issue.
  5. However, even after the prompt completes and no active prompt is running, memory continues creeping upward over time.
  6. Codex-related helper processes remain alive in the background, but their private memory does not explain the full RAM usage.

Important findings from RAMMap:

  • Total memory usage in Task Manager reached about 73%
  • Process Private: ~4.0 GB
  • Mapped File: ~11.8 GB
  • Page Table: ~5.7 GB
  • Paged Pool: ~2.46 GB
  • Nonpaged Pool: ~1.44 GB

This seems important:

  • Codex processes themselves are relatively modest in RAM usage
  • The largest Codex processes were roughly:
  • ~240 MB
  • ~156 MB
  • ~90 MB
  • ~88 MB
  • So the overall RAM problem does not appear to come from a simple Codex.exe user-space memory leak

Why I suspect a Codex-related issue:

  • Codex is the trigger: the problem starts after broad repo analysis
  • After prompt completion, Codex does not return quickly to true idle
  • Memory continues to rise slowly in the background
  • The most abnormal RAMMap metric is Page Table memory (~5.7 GB), which suggests a kernel/system-level side effect rather than a normal app-only leak

Other potentially interacting software:

  • F-Secure Endpoint Protection
  • Wargaming Game Center / wgc_renderer_h
  • OneDrive

But the issue is consistently triggered by Codex repo analysis.

Expected behavior:

  • After repo analysis completes, Codex should settle to near-idle
  • Helper/background processes should shut down or stabilize
  • Memory usage should stop growing when no active prompt remains
  • System/kernel memory (especially Page Table) should not continue growing abnormally

Actual behavior:

  • Codex analysis triggers continuing background activity
  • RAM usage keeps increasing after prompt completion
  • RAMMap shows unusually high Page Table and kernel-related memory usage

I have Task Manager and RAMMap screenshots showing the progression if needed.

What steps can reproduce the bug?

Feedback ID: 019ef5e3-22e6-7fb0-9654-08900e798282

What is the expected behavior?

not grow memory consumption

Additional information

_No response_

View original on GitHub ↗

This issue has 5 comments on GitHub. Read the full discussion on GitHub ↗