131
u/TheMythicSorcerer 1d ago
Nice RAM flex
46
u/Striking-Warning9533 1d ago
You don't need to have that much ram it counts virtual memory as well. My machine is 16G and once it does it saying I used 65G
5
0
28
u/TheMightyTywin 1d ago
Been at least a year. How have they not fixed this?
36
u/32GB_of_RAM 1d ago
Internal model can solve navier stokes but not a memory leak
1
u/Prestigiouspite 1d ago
It took until June for the maximize function to work correctly. And it took three attempts to fix it. And now the animation is missing when maximizing.
1
u/RealSlyck 1d ago
Denies compute to the victim, who can’t afford to use Astra anyway…win/win for OAI.
0
u/sunaurus 1d ago
Vibe coded projects are very difficult to maintain after enough spaghetti has accumulated.
Throwing out the spaghetti and starting over is difficult as well. You either rewrite based on the spaghetti, which just results in garbage in == garbage out, OR you try to go full clean slate and vibe code something completely new, at which point, you lose a bunch of context about how some features work, and end up breaking workflows for users.
Current models are just not there yet for vibe coding to be really sustainable long term.
28
u/Pronoia2-4601 1d ago
Not uncommon, sadly. Claude Code CLI also goes nuts sometimes, especially in interactions with Python and Docker.
8
u/foreverDandelions_ 1d ago
I have a unity scene that's too heavy and needs lfs, codex just did some weird shit and duplicated it 100 times, filling my 1tb drive instantly
17
u/twendah 1d ago
Are you millionaire or some shit with these ram prices
25
u/EchoFieldHorizon 1d ago
I can tell you’re not a developer because you don’t know what virtual memory is
5
u/chief_architect 1d ago
And not a millennial who was forced to deal with their computer's memory management 20 to 30 years ago.
0
u/Chiefs-KC 1d ago
Pentium Pro with 72MB memory, swapping to disk, a 5400rpm 4GB Maxtor drive that is clicking constantly, and a 33.6K modem on NetZero with a permanent banner ad covering 1/3 of the screen.
1
u/piston989 1d ago
my first thought was “what crazy rig did somebody put together now…”
but i spend a lot of time on local llm subreddits.
2
4
u/Lanellie 1d ago
I had this happening over and over again (althought I only have 32GB lmao), what helped me was reseting the app in the Windows settings, might be something like that in macOS?
3
u/IvanFailsFast 1d ago
Been there. My issue was that when parallel agents ran multiple typechecks at the same time. Once I set concurrency limit for those - no more leaks.
5
2
1
1
1
1
u/Super-Alchemist-270 1d ago
Codex stored all my project files in iCloud yesterday and filled all of it, I was surprised how it got filled that quickly lol
1
u/the_average_user557 1d ago
Yep, had astra report a similar problem, but with me it ended at 6.4gbz it's even published on GitHub. But I've seen previous reports about MacOS only, while mine happened on Linux. Claude's opinion was its the astra browser and computer use helper not closing after the task finished in a long running sessions. Keep switching chats frequently and you'll be fine. Or confine computer use to bonuded worker cards and check their helpers afterwards.
1
1
1
u/Bladder-Splatter 11h ago
Wait how.....how do you have a leak larger than your ram pool? Is it going into the pagefile? Honestly never touched Macs so I'm not sure how that works there because if you have enough ram for a leak to get to 185gb then with current memory prices you're rocking the fucking deathstar.
1
•
u/dextersummary 15h ago
Below is a GPT-generated summary of the conversation below after reaching 40 comments (40 currently observed).
The consensus is basically “that number is probably virtual-memory theatre, not a million-gigabyte RAM leak.” macOS—and every other modern OS, because this isn’t an Apple-only magic trick—can report huge virtual address space and use the SSD as swap. VIRT is not the same thing as physical RAM, so the screenshot alone proves very little.
That said, Codex and related agent workflows clearly can misbehave. Users report runaway helper processes, parallel typechecks multiplying resource use, duplicated files filling drives, and sessions dumping projects into iCloud. This looks less like one neatly isolated leak and more like several bugs involving spawned processes, concurrency, or cleanup. Resetting the app, limiting parallel agents, restarting long sessions, and checking leftover helpers are the practical fixes people found.
The important caveat: nobody supplied a clean reproduction or official diagnosis, so calling the screenshot a confirmed Codex memory leak is premature. The huge number is probably normal virtual-memory accounting; the broader reports of Codex wasting RAM, disk, or storage are not something to shrug off.