codex - 💡(How to fix) Fix Codex 5.4 Extra High Memory Leak [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openai/codex#17257Fetched 2026-04-10 03:43:17
View on GitHub
Comments
1
Participants
2
Timeline
3
Reactions
0
Timeline (top)
labeled ×2commented ×1
RAW_BUFFERClick to expand / collapse

What version of the IDE extension are you using?

Latest

What subscription do you have?

Pro

Which IDE are you using?

VS Code

What platform is your computer?

Darwin 25.2.0 arm64 arm

What issue are you seeing?

Unconfirmed. I use Codex at a very high throughput on Extra High Thinking on the 5.4 Model. This is all I use the computer for. I see the system data memory on my macOS has reached over 400 GB on my 500 GB machine. The more I use Codex, the more it continues to creep up until it is full and my computer crashes. I have searched through the .codex folder and it's taking up less than 2 GB of space.

I suspect that there is some place that IDE Codex might be leaking data that it uses into some system data subfolder, though I haven't actually confirmed this. Just wanted to put this out there in case anyone is facing a similar issue or has solved it before.

What steps can reproduce the bug?

I run multiple tasks at once for long periods of time on 5.4 Extra High thinking.

What is the expected behavior?

Memory that Codex utilizes to execute is cleaned up by Codex.

Additional information

No response

extent analysis

TL;DR

The issue is likely due to a memory leak in the Codex IDE extension, causing system data memory to increase over time, and a potential workaround is to close and restart the IDE periodically.

Guidance

  • Investigate the system data subfolders to confirm if Codex is indeed leaking data into these folders, which could be causing the memory increase.
  • Try closing and restarting the IDE periodically to see if this mitigates the memory creep issue.
  • Monitor system memory usage while running multiple tasks on the 5.4 Extra High thinking model to identify any patterns or correlations.
  • Consider reducing the number of tasks run concurrently or the duration of the tasks to see if this reduces the memory usage.

Notes

The issue may be specific to the combination of the latest IDE extension version, Pro subscription, and VS Code on macOS, and further investigation is needed to confirm the root cause.

Recommendation

Apply workaround: Close and restart the IDE periodically, as this may help mitigate the memory leak issue until a more permanent fix is available.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING