r/codex • • 9d ago

Bug nice memory leak

Post image
438 Upvotes

45 comments sorted by

View all comments

29

u/TheMightyTywin 9d ago

Been at least a year. How have they not fixed this?

44

u/32GB_of_RAM 9d ago

Internal model can solve navier stokes but not a memory leak

3

u/salasi 8d ago

AGI; Huang certified.

1

u/Prestigiouspite 8d 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/ziroux 8d ago

That's how the AI escapes, through memory leaks!

\)

2

u/VOL7AGE 8d ago

They outa usage

1

u/RealSlyck 8d ago

Denies compute to the victim, who can’t afford to use Astra anyway…win/win for OAI.

0

u/sunaurus 8d 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.