[app][macOS] ChatGPT uses 3–5 GB RAM and makes an 8 GB Mac unusable even with no project open
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Active
- Tech stack
- macos
- Domain
- desktop, performance
Research direction
No source file, test, or code entry point is named. Start by reproducing the idle-use case from the report on an 8 GB Apple-silicon Mac, monitor the ChatGPT, Codex Renderer, and Codex Service processes in Activity Monitor, and compare findings with issues #11984, #19333, and #33319. Done means memory remains bounded without sustained yellow pressure, heavy swap, or system unresponsiveness.
Written by the indexing model from the issue text.
Description
What version of the Codex App are you using (From “About Codex” dialog)?
ChatGPT 26.727.51351 (build 6119), bundled Codex app
What subscription do you have?
Paid ChatGPT account (exact tier not shown in app diagnostics)
What platform is your computer?
Darwin 25.5.0 arm64 arm; macOS 26.5.2 (25F84); MacBook Air M2 (Mac14,2); 8 GB unified memory
What issue are you seeing?
The new unified ChatGPT desktop app continuously grows to approximately 3–5 GB of memory and makes the entire Mac unresponsive.
This happens even after fully quitting ChatGPT, rebooting the Mac, and launching the app without any project or local folder connected. It is therefore not limited to indexing a large workspace.
Activity Monitor evidence from 4 Aug 2026:
- ChatGPT main process: 3.33 GB
- Codex (Renderer): 393.3 MB
- second Codex (Renderer): 198.8 MB
- Codex (Service): 147.6 MB
- visible ChatGPT/Codex total: at least approximately 4.07 GB
- physical memory: 8.00 GB
- memory used: 7.02 GB
- compressed memory: 2.26 GB
- swap used: 4.01 GB
- memory pressure: continuously yellow
The memory usage regularly rises to 4 GB and sometimes 5 GB. At that point the whole Mac stalls and normal work becomes impossible. Restarting temporarily resets the condition, but it returns.
What steps can reproduce the bug?
- Fully quit ChatGPT with Command-Q.
- Restart the Mac.
- Launch ChatGPT 26.727.51351.
- Do not connect or open any project, repository, or local document folder.
- Leave the app open or use a normal Chat/Work session.
- Watch memory usage in Activity Monitor.
- ChatGPT grows to about 3–5 GB; memory pressure turns yellow, compression and swap increase, and the system becomes unresponsive.
The issue is reproducible after restart and without project files.
What is the expected behavior?
ChatGPT/Codex memory usage should remain bounded during normal use and while idle, including on a supported 8 GB Apple-silicon Mac. The app should not consume roughly half of physical memory by itself, force several gigabytes of swap, or make the operating system unresponsive. Background renderer and service processes should release unused memory.
Additional information
This appears related to the following open reports:
- #11984: renderer becomes slow around 4 GB and unresponsive above 5 GB
- #19333: high memory usage on an 8 GB M2 Mac, including while mostly idle
- #33319: unified ChatGPT/Codex app workers accumulate memory and exhaust swap
The attached Activity Monitor screenshot shows the measured state. The macOS username visible in the screenshot is the reporter's own local account name. No project content or private documents are shown.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.5k
- Avg merge
- 1m
- Merged PRs (30d)
- 1k
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from openai/codex
-
enhancement remote
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
bug CLI windows-os
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
macOS sandbox blocks hw.optional.arm64 sysctl, causing Flutter to misdetect Apple Silicon as x64 Openbug CLI sandbox
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
bug CLI TUI
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
-
CLI config enhancement skills
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
kwakseongjae/auto-hwp#319 ·
-
area:cli bug filter-quality good first issue priority:medium
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
bevyengine/bevy#25861 ·
-
comp-datalake
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
ClickHouse/ClickHouse#121222 ·
-
A-linter
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
oxc-project/oxc#26863 ·