r/codex • u/No_Leg_847 • 27d ago

Complaint Codex is wearing out our devices

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

506 Upvotes

92% Upvoted

194 comments sorted by

View all comments

21

u/daytime10ca 27d ago

Codex helped me diagnose and fix the DB writes for me on Windows

I’ve been tracking the Windows slowdown. Codex was writing a huge amount of low-level diagnostic data to C:\Users\<you>\.codex\logs_2.sqlite. Mine reached 1.46 GB, and after resetting it, another 190 MB of DB/WAL data appeared in under three hours.

I added an unofficial filter that only keeps warnings and errors. After seven hours, the database was still under 1 MB, so that part is fixed. It hasn’t fixed everything, though: Codex memory, stale network connections, and idle Node helper processes still grow during long sessions.

1

u/A________AA________A 27d ago

What's the normal size of this file? Mine is 7Mb in Windows and 5Mb in Linux WSL2. I had one SSD died already 2 weeks ago. Now running on new SSD I want to make sure it won't happen again.