- cross-posted to:
- programmerhumor@lemmy.ml
- cross-posted to:
- programmerhumor@lemmy.ml
A screenshot from youtube, Virbox
The line causing the memory leaks is actually the lack of a line:
free()
.This is why I only allocate on the stack
Stack overflow intensifies
Based nasa compliant engineer
This guy gets it
Static allocation for the SIL ratings
People who are enthusiastic about using pointers in C++ are doing it wrong. Never use a pointer when you can get away with a reference.
For C++, yes. But “reference” is just a way of using the pointer when it comes to C
Sure, but that’s technically allocation-agnostic either way.
I only use the registers.
rip random amiga machine
Eh… ship it. RAM is cheap.
“Uh, Boss, our customers are sending us the invoices for their RAM purchases.”
OMG I SHOULD HAVE DONE THAT TO JETBRAINS AND MICROSOFT FOR TEAMS
Also electron. Because somehow a full blown separate FF instance is more ram efficient than electron.
Well, Electron uses Chrome, so yes
~I’m sorry~
That’s why I preallocate the max memory I will need just like I was taught to do in Fortran. You can’t leak what you don’t have.
Heap allocation failure > gradual memory leak
Checkmate atheists.