Give me five reasons why I should free() when the OS will reclaim the memory anyways or I kill this anime blob.
Give me five reasons why I should free() when the OS will reclaim the memory anyways or I kill this anime blob
Aiden Moore
Other urls found in this thread:
en.m.wikipedia.org
en.m.wikipedia.org
twitter.com
Gabriel Anderson
It's a good practice.
Justin Davis
americans really love gun violence eh
Andrew Carter
Not freeing is a viable strategy for short lived processes. This is often actually done e.g. in compilers.
Eli Rogers
your program will have to die before the memory is reclaimed you stupid nigger
it's like asking why you should clean your own room when it won't matter after you blow your brains out
James Moore
Sounds more like your compiler is shit.
Wyatt Bell
Not five reasons
Colton Brown
- OS may not reclaim memory on process exit (on modern OSes, happens with shared memory)
- if it does, then it's still memory that could have been used for something else
- you may run out of memory before execution completes, and the OS will kill your process
- it may keep the pages mapped in process memory, making future allocations faster
- in multithreaded environments, concurrent allocation and de-allocation operations can be optimized to complete faster
Joshua Sullivan
Can I eat the remains?
Jack Allen
Hudson Barnes
Just never free(). See what happens. Remember to mention "btw I never free()" in CV and during interviews. Remove yourself from the workforce.
Josiah Torres
Rust doesn't have this problem.
Easton Sanders
it's okay, bro, just run this code
Wyatt Murphy
Fuck i forgot the pic
Chase Miller
>five reasons
imposible, anyway...
good pratice
you can develop a bad habit if not used
crashes on atexit
[filler space]
bad for shared resources
Jackson Gray
I see memory leaks when I run gcc through valgrind
Robert Stewart
>black bullets
why?
Andrew Murphy
whyte wimminz love da big black cartridge
Kevin Wright
Viruses can steal ur bits
Chase Williams
The OS won't reclaim the memory until after the program is done with it, which happens when it's freed or when the program exists.
The OS, compiler or anything else can't compensate for shit code.
Ayden Turner
>gcc
>not shit
LMAOing at you