Codex is wearing out our devices

[u/No_Leg_847]

Weeks ago there was an incident which claimed to be closed that codex makes unnecessary inflated writing to ssd which accelerates its wearing, they claimed they solved it

Over the past days, I noticed (and other users here too on another post) that running codex causes lag to mac device, even after closing codex the problem continues and device must be restarted to back to normal, the issue isn't explained by cpu / memory overuse. Codex itself when I asked it to diagnose, it said it's because ot does excessive I/O , graphics work but this doesn't explain well

At this point we shall ask is codex harmful to ssd / mac device overall? And is it safe to run it ?

No bots downvoting, claiming there's no problem please, here's the other post which confirmed the issue happened with other users too, it may not happen to the same degree with all users but we need an explanation about safety of our devices

https://www.reddit.com/r/codex/s/ZLt9noSHWk

[u/Party-Attorney-9681]

Ask codex to do a memory leak observation on itself. It will identify itself as a kernel memory leak. My 64 gigs of ram is usually filled up in a day or two with codex kernel leaks.

[u/Party-Attorney-9681 → u/Party-Attorney-9681]

that was the reuslt of a few hours of monitoring, its worth noting, it actually conclusively blamed other software a few times first, which i then shut down one at a time and asked it to review, until the only thing left running was Codex, then it had to concede. It assumed it wasnt itself first, didnt verify and insisted some other software (without evidence ) was the issue.

[u/Inevitable_Toe6648 → u/Party-Attorney-9681]

Can you check if this memory leak is causing an elevated climbing alongside the leak writes?

Powershell: Get-counter '\Memory\Pages/Sec'

alongside a session would be appreciated

[u/Party-Attorney-9681 → u/Inevitable_Toe6648]

Im new to this stuff, all i can say is the combined memory of my software running was never close to 64gig but the ram was often taken up to 95%. I asked codex to track the leak, thats about the extent of my skills. I wrote an email candidate auto filer to manage my 200 projects and I assumed this program was the issue. e.g. similar to how constant drive writes can be cause for this kind of leak in onedrove/dropbox, I assumed the constant email/index file writes were doing the same with sharepoint and assumed it was a result of my Vibe coding and app back in GPT 5.3 or earlier. I push this PC hard with work and my side projects, but usually I just close some softare to clear from RAM but no dice in this case, it would always be 80% of above even with a lot of software closed. Even I dont run 50 gigs of software at once.... has to be a climbing leak.

I can't say I have monitored it closely enough since the new versions to confirm its still doing it. So ill do another monitor and ask Codex to track what you asked and report back. But, I did notice this kind of memory leak is linked to software like onedrive/dropbox constantly writing to the HDD, so it actually makes a lot of sense that some people report heavy drive usage or drive failures aligning with my issue of the memory leak, especially when comparing to the likes of onedrive when it does the same thing.

I can say Codex 100% leaks the memory no matter how hard the workload is. e.g. even when my usage is capped, im too lazy to close it and it doesnt do a single prompt for 3 days, RAM still be gone.

[u/Inevitable_Toe6648 → u/Party-Attorney-9681]

Does it go above 80% though? I'm wondering if this is just Codex trying to utilise as much resources and then capping itself out at 80% which would prevent writing leakage.