TL;DR
Get business pricing on monitors, keyboards and dev gear
- Business-only prices and quantity discounts
- Tax-exempt purchasing
- Multiple users, one account, clear invoices
A Codex Desktop user reported that Crashpad folders grew to about 323GB over measurements taken from Oct. 15 to Oct. 17, 2026, leaving 1.4GB free on a 926GB Mac. The report is an individual user’s account on GitHub; OpenAI has not provided a response in the supplied material, and the cause and scope of the issue are not confirmed.
A Codex Desktop user reported that the app’s Crashpad folders occupied about 323GB on a Mac, consuming roughly 35% of a 926GB disk and leaving only 1.4GB free. The measurements, posted on GitHub for Oct. 15–17, 2026, describe one user’s system and do not establish how widespread the problem is or confirm its cause.
The reporter said the two folders were under ~/Library/Application Support/com.openai.codex/web/Crashpad and ~/Library/Application Support/Codex/Crashpad. The first reportedly contained 2,251,765 files and occupied 180GB; the second, with most of its contents in a pending subfolder, held 1,785,095 files and occupied 143GB. Together, they amounted to about 4.04 million files and 323GB, according to the post.
The report identifies the environment as ChatGPT.app 26.1007.71326, build 20398, with Codex Framework (Chromium) 155.0.8059.40, macOS 15.7.4 and an Apple Silicon arm64 processor. The user said the app continued working and gave no warning about the storage use. They said they discovered the files by checking the Library folder’s disk usage.
For cleanup, the reporter said they renamed both Crashpad folders while the app remained open, then deleted the renamed copies. Available space increased from 1.4GB to more than 50GB within minutes, while deletion was still underway. The post asks for limits and automatic pruning, a fix for what the user describes as a crash loop, and an in-app warning when app data grows beyond a few gigabytes.
If the report reflects behavior other users also encounter, unchecked dump accumulation could consume storage needed by other apps and system tasks without making the cause apparent to users. In this instance, the reporter says free space fell to 1.4GB before they identified the Crashpad directories. That is a substantial impact on the affected machine, even though a single report cannot show how often the issue occurs.
The report also highlights a gap between an application remaining usable and its background data remaining within reasonable bounds. The user said Codex continued to work while millions of files accumulated. A storage cap, automatic cleanup or clear warning could help users identify and manage growth before disk space becomes scarce, but the source material does not establish whether any such change is planned.
As an affiliate, we earn on qualifying purchases.
Earlier Crashpad Reports and Requests
The GitHub issue was first titled “Codex Desktop continuously generates Crashpad pending dumps, growing to ~5GB,” then retitled on June 9, 2026, to say the growth was “without any limit: +5GB per day at least.” The latest supplied update says the issue was still happening on the current build and reports much larger measurements from Oct. 15–17. These are user-provided observations, not independently verified measurements.
The reporter links several related GitHub issues, including one describing Crashpad handler SIGTRAPs shortly after launch and a reported rate of about 17GB per day. Other linked issues concern Codex-generated data storage limits and automatic cleanup. Those references show that users have raised related concerns, but they do not establish that the same cause explains the 323GB accumulation in this report.
“Still happening on the current build, and at a much larger scale.”
— The GitHub issue reporter, describing the latest measurements
As an affiliate, we earn on qualifying purchases.
Scope and Cause Remain Unverified
The supplied source is an individual GitHub report. It does not include an independent inspection of the Mac, a response from OpenAI, or evidence that other users have experienced the same volume of accumulation. The measurements also do not establish precisely when the files were created or how quickly the total grew across the full period; the title’s daily-growth wording is the reporter’s characterization.
The user associates the buildup with Crashpad pending dumps and points to a related issue about handler crashes, but the material does not confirm that a crash loop caused the reported files. It is also unclear whether the files in both directories share one cause, whether the behavior persists outside the stated software and operating-system versions, or whether a fix or cleanup mechanism is already available.
automatic disk cleanup software for Mac
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Awaiting a Maintainer Response
The next clear development would be a response on the GitHub issue from OpenAI or a project maintainer addressing the reported storage growth, its cause and whether users should take any action. The reporter has requested automatic pruning, a storage cap and an in-app warning; the supplied material does not say whether those requests have been accepted or scheduled.
Users following the report can look for updates to the original issue and its linked discussions. Until a maintainer confirms a fix or provides guidance, the source does not establish that the reported behavior affects every installation or that renaming and deleting the folders is an approved remedy.
As an affiliate, we earn on qualifying purchases.
Key Questions
How much storage did the user report that Crashpad files used?
The user reported about 323GB across two Crashpad folders: 180GB in one and 143GB in the other. The folders reportedly contained about 4.04 million files combined.
When were the measurements taken?
The GitHub report says the measurements were taken from Oct. 15 to Oct. 17, 2026, on ChatGPT.app 26.1007.71326, build 20398, with macOS 15.7.4 on Apple Silicon.
Does the report prove Codex Desktop has a widespread storage problem?
No. It documents one user’s experience. The supplied material does not establish how many users are affected or independently verify the measurements.
Did OpenAI confirm a cause or announce a fix?
No response or fix announcement is included in the source material. The reporter links a separate issue about Crashpad handler crashes, but the cause of the reported 323GB buildup is not confirmed.
What changes is the reporter asking for?
The user asks for a size or file-count limit on pending dumps, automatic cleanup, a fix for the suspected handler crash loop, and an in-app warning when Codex data grows beyond a few gigabytes.
Source: hn
Halloween Picks
halloween
As an affiliate, we earn on qualifying purchases.
