Should I free memory before exit?

by

This is actually a really hard, imponderable question.

Pro (in favor of freeing everything before exit):

  • no bugs or memory leaks later if code is rearranged
  • no false positives from valgrind or memory leak checker
  • no memory leaks if you’re running under a buggy OS, or no OS at all

Con (just exit, don’t worry about freeing everything):

  • freeing everything can be a lot of work
  • freeing everything can introduce bugs and crashes
  • your OS really, really ought to reclaim all resources for you when you exit

And, one more point (not sure if it’s a pro or a con): on the majority of systems, calling free does not return memory to the Operating System (only exiting does that).

In the end, you will have to decide which of these pros and cons matters most for you. Different programmers on different projects under different circumstances will reach different conclusions; there is no one-size-fits-all answer here.

See also this previous Stack Overflow question.
See also question 7.24 in the C FAQ list.

More Related Contents:

  1. What REALLY happens when you don’t free after malloc before program termination?
  2. How do free and malloc work in C?
  3. Setting variable to NULL after free
  4. free char*: invalid next size (fast) [duplicate]
  5. C – Accessing data AFTER memory has been free()ed?
  6. malloc implementation?
  7. If free() knows the length of my array, why can’t I ask for it in my own code?
  8. Why do I get different results when I dereference a pointer after freeing it?
  9. C: Correctly freeing memory of a multi-dimensional array
  10. Is freeing allocated memory needed when exiting a program in C
  11. Problem usage memory in C
  12. Why exactly should I not call free() on variables not allocated by malloc()?
  13. How are we able to access the pointer after deallocating the memory?
  14. Code for malloc and free
  15. Why this program is crashing?
  16. How can I get the size of an array from a pointer in C?
  17. Why is it safer to use sizeof(*pointer) in malloc
  18. Overriding ‘malloc’ using the LD_PRELOAD mechanism
  19. Using malloc for allocation of multi-dimensional arrays with different row lengths
  20. Writing to pointer out of bounds after malloc() not causing error
  21. Is the compiler allowed to recycle freed pointer variables?
  22. C Warning: Function returns address of local variable
  23. malloc(sizeof(int)) vs malloc(sizeof(int *)) vs (int *)malloc(sizeof(int))
  24. Why do I get a warning every time I use malloc?
  25. An alternative for the deprecated __malloc_hook functionality of glibc
  26. Why does this intentionally incorrect use of strcpy not fail horribly?
  27. Minimizing the amount of malloc() calls improves performance?
  28. new, delete ,malloc & free
  29. Malloc and array index confusion in C
  30. zero size malloc [duplicate]

Leave a Comment