Codex Causes Frontend Dev Server Startup to Hang and Memory Usage to Exceed 50GB on Mac
What version of the Codex App are you using (From “About Codex” dialog)?
26.519.41501 (3044)
What subscription do you have?
- 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?
- Open a frontend project in Codex.
- Do not enable or use any Codex skill.
- Run the frontend project locally, for example with
npm run dev. - Observe that the dev server startup becomes extremely slow or hangs.
- Check system memory usage in Activity Monitor.
- Memory usage increases rapidly and can exceed 50 GB.
- The Mac eventually freezes or becomes unresponsive.
What is the expected behavior?
_No response_
Additional information
_No response_
2 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
I reviewed #24354. This issue is related, but not an exact duplicate.
The previous issue is about the problem happening when a Codex skill is used. In this case, the same frontend startup hang and memory usage over 50GB can also happen without using any skill.
So I believe this should remain open as a broader Codex App performance/memory issue.