codex - 💡(How to fix) Fix Codex Causes Frontend Dev Server Startup to Hang and Memory Usage to Exceed 50GB on Mac

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…
RAW_BUFFERClick to expand / collapse

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

26.519.41501 (3044)

What subscription do you have?

  1. Open a frontend project in Codex. 2. Do not enable or use any Codex skill. 3. Run the frontend project locally, for example with npm run dev. 4. Observe that the dev server startup becomes extremely slow or hangs. 5. Check system memory usage in Activity Monitor. 6. Memory usage increases rapidly and can exceed 50 GB. 7. The Mac eventually freezes or becomes unresponsive.

What platform is your computer?

No response

What issue are you seeing?

When using Codex with my frontend project, the dev server startup becomes extremely slow or completely hangs, even when no Codex skill is used.

The issue happens when I run the frontend dev server, for example with npm run dev. Memory usage increases rapidly and can exceed 50 GB, eventually causing my Mac to freeze or become unresponsive.

This does not seem to be limited to a specific skill. It can also happen without using any skill, so the issue may be related to Codex scanning, indexing, watching, or processing the project files.

The project contains typical frontend directories such as node_modules, .next, dist, or build cache folders. It looks like Codex may be consuming excessive memory when handling the project workspace.

What steps can reproduce the bug?

  1. Open a frontend project in Codex.
  2. Do not enable or use any Codex skill.
  3. Run the frontend project locally, for example with npm run dev.
  4. Observe that the dev server startup becomes extremely slow or hangs.
  5. Check system memory usage in Activity Monitor.
  6. Memory usage increases rapidly and can exceed 50 GB.
  7. The Mac eventually freezes or becomes unresponsive.

What is the expected behavior?

No response

Additional information

No response

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