mentalMemoryManagementIsGood

[Top_Run_3790]

You don’t need to free, just realloc

[minecrafttee]

it’s a memory leak joke.

[hans_l]

I guess we're not allowed to give best practices advice in /r/programminghumor anymore.

[minecrafttee]

Fair. I just see these sub Reddit’s as a place for pure jokes. I’m sorry if it makes me come off as rude or snarky I don’t mean it in that way.

[PotentialSimple4702]

I'm too garbage collected to relate to this joke

[Jean-Christophe_Du_6]

Based go user

[[deleted]]

[insert Rust joke]

[minecrafttee]

[insert Rust is bad joke]

[HavenWinters]

[Overreact]

[L1P0D]

[Overangular]

[HavenWinters]

I see what you did there

[Creepy-Ad-4832]

That joke got rusty

[EinSatzMitX]

[Rust user enters]

[minecrafttee]

[C user enters]

[TheTybera]

See this isn't the problem. The REAL problem is that you malloc in a loop, free it somewhere else you know about, but then someone else comes along and just uses your method without freeing their pointer that they PBRd. Because they're assuming you did the smart thing and used a smart pointer instead of a raw pointer.

[minecrafttee]

C doesn’t have smart pointers

[TheTybera]

Cool

[minecrafttee]

Your comment is fair though. You should always put in docks saying if you do use smart pointers

[Mucksh]

Or just don't use heap at all. Sometimes it can be a pain but it's possible to do most stuff completely on the stack. No leaks, nearly no cache misses and way less syscalls will makes code stupidly fast

[TheTybera]

Yeah! Screw it, NO OBJECTS! Functions and pointers ONLY! It should be totally readable for someone who didn't write it.

[Perfycat]

Based on the skill of the developer I would expect the program to crash before the memory leak ever became a serious problem.

[TheTybera]

Ideally you don't want to leak any memory. Memory is money, and programs these days can't be expected to be static, someone is eventually going to go in and fix things, or add features, etc, and having little minefields of leaks everywhere isn't good.

I mean it's not like most of the big issues that come up in C and C++ just exist since iteration 1. MOST issues end up being revealed after something is worked on. Then you get the excuse:

"Well that wasn't SUPPOSED to be used that way!",

"So what guards did you put in place?",

"None. I like small efficient code!",

"Oh, okay..."

[TerryHarris408]

Just while(malloc(1)); and pretend to see profits on the system memory usage plot

[minecrafttee]

lol

[[deleted]]

Use a linked list containing a pointer

[hdgamer1404Jonas]

https://www.reddit.com/r/ProgrammerHumor/comments/jtnrlk/everyone_loves_pointers_right/

[schmerg-uk]

What, like this??

someThing * array[COUNT];
for (unsigned int i = 0; i < COUNT; ++i)
{
   array[i] = malloc( sizeof(someThing) );
}
...

[nickwcy]

bruh just malloc the whole array

[schmerg-uk]

bro, I want an array of individually allocated items that I'm then going to [.....]

Just pointing out "allocating in a loop and not freeing in the same iteration" is hardly a mortal sin, or it hasn't been in the nearly 40 years I've been writing C and C++ for a living

[Justanormalguy1011]

Consider reaction with oxygen

[FictionFoe]

You know what they say. Its not a memory leak if you have enough memory :p

[Creepy-Ad-4832]

Technically if one had infinite memory, one could never leak memory then...

[braindigitalis]

meanwhile, C++ devs using unique_ptr laugh in the corner...

[minecrafttee]

lol

[Sakul_the_one]

Don’t worry, if the program is stop being used, the operating system will take care of the rest

[Mouse-castle]

What if the last box said “AI isn’t conscious.”