Live data from Hacker News

Codex logging bug may write TBs to local SSDs

github.com

251–260 of 296 posts

Re: Codex logging bug may write TBs to local SSDs

#251
post #57
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…

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???

Plot twist: the companies are unethically (blaming it on AI slop code) harvesting your GPU and CPU resources to generate tokens for their products consumers in a decentralized fashion. Not unlike those old monero or other crypto spyware miners.

Re: Codex logging bug may write TBs to local SSDs

#252
post #237

Earlier quoted context omitted.

So there's this amazing thing called a symlink

Not amazing enough. Let me present you claude-md-symlinker [1], an 8k-lines Rust project designed to do exactly the same as a symlink but in an obscure manner, running as a Linux service and maintaining its own database. This is like left_pad but for symlinks. [1]: https://github.com/dutifuldev/claude-md-symlinker#claude-md-... (I’m not the author obviously)

Haven’t even had my coffee yet and this is definitely the most cursed thing I’ll see today, thanks!

Re: Codex logging bug may write TBs to local SSDs

#253
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"?

> shouldn't this "agentic AI revolution" have long solved this already? Daily reminder that Anthropic took over a year to fix the Claude Code terminal flickering issue despite proclaiming all over the internet that software development as a "solved problem." Apple forked over $250 Million in a class action over false advertising for Apple Intelligence. When do we start seeing the same for the misleading and outright…

Why is not a thing that people track the lies of people as they are public, and tie them to their reputation over time for anyone to find?

Re: Codex logging bug may write TBs to local SSDs

#255
post #156

Earlier quoted context omitted.

> It still boggles my mind that Anthropic would invent the MCP protocol but not fully implement it. https://www.joelonsoftware.com/2002/01/06/fire-and-motion/ > Do they just want to force you to keep busy reacting to their volleys, so you can’t move forward?

> ...Do they just want to force you to keep busy Given functionally unlimited access to tokens with frontier models, there is really no "force you to keep busy"; it should just bake overnight. We're talking about a rather simple and well-defined specification; not something novel and complex.

My point is that there is a chance that Anthropic launched MCP:

1. not fully believing in it

2. but knowing the hype around MCP would force other AI labs to implement it (standard enterprise checkbox behavior)

3. thus wasting some of their competitors' development cycles

* * *

And let's be real here, the entire discussion happens in the context of a basic bug in a coding agent, do we really believe that these labs have hit AGI in coding?

Random example:

Go to claude.ai or gemini.google.com (I imagine OpenAI is in a similar situation).

Type a question, press enter. Wait 2 seconds, then turn on airplane mode.

Not only does the connection cut off, but even if you reconnect 20 minutes later, you still won't get the answer.

Their website works in purely sync mode!!!

We knew better than this when HTML was invented, 30 years ago.

Do their products give you the impression than "baking features with unlimited tokens overnight" leads to decent products?

Re: Codex logging bug may write TBs to local SSDs

#256

Earlier quoted context omitted.

the damn chat.openai.com webapp lags a lot as well on long chats, typing takes so long.

I believe this is because they don’t lazyload the document. The entire conversation sits in the DOM.

Yeah - is such a large dom of essentially text expected to be that slow?

For what it's worth I use a small script that essentially deletes old chat messages DOM nodes which significantly speeds it up.

Re: Codex logging bug may write TBs to local SSDs

#257
post #158
post #82

Earlier quoted context omitted.

Right, just yesterday I found my laptop kinda hot. And what do you think, it was good old Claude deciding to load a few cores with completely idling prompts.

Yeah, somehow claude-cli sitting in a tmux session doing nothing uses my laptops battery twice as fast. Powertop suggests a ton of wakeups, but why? Is it busy polling the input or something?

Polling the Department of Trade for Order 66

Re: Codex logging bug may write TBs to local SSDs

#258
post #14

This thread will become a typical "haha slop company made slop" but I've been bitten by a bug exactly like this before in a (pre-AI, artisan) OSS project. The maintainer there didn't properly account for DST when calculating last backup time, so the app started and never stopped writing/re-writing backups continuously. Perhaps the framing shouldn't be "haha slop" but rather why doesn't the AI write better quality sof…

What are your thoughts on the SNR of the linked GitHub issue threads? Consider the volume of comments posted and the substance of each comment.

My gut reaction is "I wish they'd just get to the point". Tbf some people would probably react the same way to my issue thread on the bug that I hit [0].

[0]: https://github.com/mnemosyne-proj/mnemosyne/issues/99

Re: Codex logging bug may write TBs to local SSDs

#259

Earlier quoted context omitted.

> I don't think we should ever head toward licensing/a credential body for software development, but I do think now is a good time to have discussions around liability for defective products. Liability is how a credential body would organically grow. It already exists in the security, compliance, and enterprise parts of the software world.

That can be okay. The problems we're worried about come when it's government mandated. The EU Cyber Resilience Act puts heavy liability on vendors for software vulnerabilities that get exploited, including in open-source components they incorporate. OSS devs are shielded - liability is on the companies who incorporate OSS into commercial stuff.

In practice, what’s the difference between a government mandated license and a government that quickly rules in favor of parties who are damaged by companies that don’t use licensed software engineers?

E.g. “Your software caused serious damages to our company / livelihood, and you best hope that it turns up in discovery that you used properly licensed software engineers who were following licensing best practices, otherwise this will be a slam dunk case.”

Genuinely an interesting question to me. Seems like the latter is a better option, generally, but it does lock restorative justice behind a paywall - you have to be able to afford a lawyer.

Re: Codex logging bug may write TBs to local SSDs

#260
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!!

Ah, so they ported that feature over from ChatGPT?

Post reply on HN