Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Codex logging bug may write TBs to local SSDs

github.com

Post reply on HN
Print view View original

131–140 of 296 posts

Re: Codex logging bug may write TBs to local SSDs

#131

Post by coldtea »

veber-alex wrote: post #96
nicce wrote: post #57

Earlier quoted context omitted.

Not only Codex, but I can't leave ChatGPT app in macOS open for few hours, because it will consume 60 gigabytes of RAM over time and crashes all the apps. Mindboggling. Or can't use Google's AI Studio in browser because it takes 100% CPU. Need to write own app for everything???

ChatGPT works ok for me but Whatsapp consumes 1000% cpu after the mac wakes up after sleep. I swear a few years ago shit like this didn't happen on macOS.

A few years ago vibe-coded crap apps like that didn't exist on macOS.

Re: Codex logging bug may write TBs to local SSDs

#132

Post by theowaway213456 »

altcognito wrote: post #123

I think part of the question should be, why is there no QA or test that catches this? It's one thing to be slopware, but why didn't anything run a test that catches this?

Every time you write a test that handles some data, you write an assertion about how much data is handled?

Come on, this is such an easy thing to forget to test. Don't act like there is some magical testing strategy that would have caught this

Re: Codex logging bug may write TBs to local SSDs

#133

Post by ValentineC »

me551ah wrote: post #122
jofzar wrote: post #41

Earlier quoted context omitted.

> Codex is one of the most infamous examples of slopware Woah, let's not forget Claude code is right there

Claude is also weird for being the only coding assistant that for some reason doesn't support AGENTS.md. Codex, Amp, Cursor all of them support it and read from it, but not claude which forces it's users to use CLAUDE.md instead. The issue is the higest voted issue on their gitlab repo: https://github.com/anthropics/claude-code/issues/6235

My CLAUDE.md is just:

    @AGENTS.md
And Claude processes it just fine.

(I see that it's a common workaround, and there's a comment in the above link saying just this: https://github.com/anthropics/claude-code/issues/6235#issuec...)

It's a hassle having to add it to every repo that I use Claude with though, and I often use other models and harnesses too for the more trivial tasks.

Re: Codex logging bug may write TBs to local SSDs

#134

Post by coldtea »

seviu wrote: post #61
b--l wrote: post #10

Codex is one of the most infamous examples of slopware. Just having the window unhidden on my mac will cause it to use 100% of the GPU displaying the spinner message. THE SPINNER MESSAGE CAUSES 100% GPU USAGE ON AN MBP M5!! So any time you're waiting on the model (which is 90% of the time), your fans will be blasting (careful, don't use it on battery). The issue is on github and close to 6 months old. Probably since…

To be fair with Codex, you can use any harness you want with it. Access is not gatekeeper by a crappy full of slop electron app. So just move to PI, or whatever. Claude on the contrary, forces all plan users to use their horrible app, which, if you ever dared to use cowork, only once, will run a 2GB VM on app start, no f's given. at all. Not justifying it. But if you use the official Codex app, thats on you. If you u…

>if you ever dared to use cowork, only once, will run a 2GB VM on app start, no f's given. at all.

Of all the issues, this seems like the most tame. I mean, there are single Chrome tabs that can use 300MB or even 700MB. A 2GB VM for what is likely isolated local testing of scripts and commands or local lightweight first-level inference to help guide the main harness sounds reasonable.

Re: Codex logging bug may write TBs to local SSDs

#135

Post by anon373839 »

me551ah wrote: post #122
jofzar wrote: post #41

Earlier quoted context omitted.

> Codex is one of the most infamous examples of slopware Woah, let's not forget Claude code is right there

Claude is also weird for being the only coding assistant that for some reason doesn't support AGENTS.md. Codex, Amp, Cursor all of them support it and read from it, but not claude which forces it's users to use CLAUDE.md instead. The issue is the higest voted issue on their gitlab repo: https://github.com/anthropics/claude-code/issues/6235

[flagged]

Re: Codex logging bug may write TBs to local SSDs

#136

Post by sgarland »

woadwarrior01 wrote: post #17

Someone posted a temporary workaround for this on X[1]. sqlite3 ~/.codex/logs_2.sqlite "CREATE TRIGGER IF NOT EXISTS block_log_inserts BEFORE INSERT ON logs BEGIN SELECT RAISE(IGNORE); END;" Also, I found that running VACUUM FULL on the sqlite file on my laptop shrunk it from 27GB to a mere 73MB[2]. [1]: https://xcancel.com/bdsqlsz/status/2067964486615810369 [2]: https://xcancel.com/jeethu/status/2068087449469780434

DB-level rules saving the day once again.

Re: Codex logging bug may write TBs to local SSDs

#137

Post by ValentineC »

r_lee wrote: post #64
b--l wrote: post #10

Codex is one of the most infamous examples of slopware. Just having the window unhidden on my mac will cause it to use 100% of the GPU displaying the spinner message. THE SPINNER MESSAGE CAUSES 100% GPU USAGE ON AN MBP M5!! So any time you're waiting on the model (which is 90% of the time), your fans will be blasting (careful, don't use it on battery). The issue is on github and close to 6 months old. Probably since…

if we are at 10x with AI and near AGI or ASI, then how is it possible that these products (Codex, Claude Code CLI) are still such garbage? shouldn't this "agentic AI revolution" have long solved this already? no way they're over there saying "we are on it plz wait" or that "it's too much effort"?

The "AI revolution" feels like it's creating a bunch of ultra-smart AI models are scarily good at cracking most of human-created security (Mythos), but also happen to be careless snobs that just leave litter and mess in their wake.

Re: Codex logging bug may write TBs to local SSDs

#138

Post by CryZe »

b--l wrote: post #10

Codex is one of the most infamous examples of slopware. Just having the window unhidden on my mac will cause it to use 100% of the GPU displaying the spinner message. THE SPINNER MESSAGE CAUSES 100% GPU USAGE ON AN MBP M5!! So any time you're waiting on the model (which is 90% of the time), your fans will be blasting (careful, don't use it on battery). The issue is on github and close to 6 months old. Probably since…

> THE SPINNER MESSAGE CAUSES 100% GPU USAGE ON AN MBP M5!!

This seems to be a common Chromium problem across tons of software. GitHub has the same issue with its spinners, VSCode as well.

Re: Codex logging bug may write TBs to local SSDs

#139

Post by tartoran »

mnicky wrote: post #105
r_lee wrote: post #64

Earlier quoted context omitted.

if we are at 10x with AI and near AGI or ASI, then how is it possible that these products (Codex, Claude Code CLI) are still such garbage? shouldn't this "agentic AI revolution" have long solved this already? no way they're over there saying "we are on it plz wait" or that "it's too much effort"?

If the code churn is high the investment to refactoring etc is less beneficial than may be obvious. I don't remember the details but I heard in some podcast that the code base of Claude Code changes so fast that any piece of code won't be there for long..

If they respected their users they’d at least pin some versions that are more stable.

Re: Codex logging bug may write TBs to local SSDs

#140

Post by matheusmoreira »

christophilus wrote: post #101
purpleidea wrote: post #63

I want to like codex, but the quality is just not very good, especially when compared to Claude. It used to work okay, but a while back they landed a major regression for an entire team of folks I work with. No response, no workaround. https://github.com/openai/codex/issues/23762

I don’t trust any agent to respect any boundaries. They might today. But tomorrow’s vibe coded slip update might break it in subtle ways. My solution to this is to only run agents in a sandbox of my own making (a locked down Podman container).

I went the full virtual machine route. Just finished hardening the setup and firewalling it off my local network. Not perfect but it does make me feel much safer.
Post reply on HN