Is free() zeroing out memory?

by

There’s no single definitive answer to your question.

  • Firstly, the external behavior of a freed block will depend on whether it was released to the system or stored as a free block in the internal memory pool of the process or C runtime library. In modern OSes the memory “returned to the system” will become inaccessible to your program, which means that the question of whether it was zeroed-out or not is moot.

(The rest applies to the blocks retained in the internal memory pool.)

  • Secondly, there’s little sense in filling freed memory with any specific value (since you are not supposed to access it), while the performance cost of such operation might be considerable. Which is why most implementations don’t do anything to freed memory.

  • Thirdly, at debugging stage filling freed memory with some pre-determined garbage value can be useful in catching errors (like access to already freed memory), which is why many debug implementations of standard library will fill freed memory with some pre-determined value or pattern. (Zero, BTW, is not the best choice for such value. Something like 0xDEADBABE pattern makes a lot more sense.) But again, this is only done in debug versions of the library, where performance impact is not an issue.

  • Fourthly, many (most) popular implementations of heap memory management will use a portion of the freed block for its internal purposes, i.e. store some meaningful values there. Which means that that area of the block is modified by free. But generally it is not “zeroed”.

And all this is, of course, heavily implementation-dependent.

In general, your original belief is perfectly correct: in the release version of the code a freed memory block is not subjected to any block-wide modifications.

More Related Contents:

  1. Why do I get different results when I dereference a pointer after freeing it?
  2. Should C compilers immediately free "further unused" memories? [closed]
  3. How can I indicate that the memory *pointed* to by an inline ASM argument may be used?
  4. Does free(ptr) where ptr is NULL corrupt memory?
  5. What does this GCC error “… relocation truncated to fit…” mean?
  6. Where is PATH_MAX defined in Linux?
  7. How to verify if a void pointer (void *) is one of two data types?
  8. malloc implementation?
  9. memory alignment within gcc structs
  10. Fused multiply add and default rounding modes
  11. Status of __STDC_IEC_559__ with modern C compilers
  12. C: Correctly freeing memory of a multi-dimensional array
  13. Is freeing allocated memory needed when exiting a program in C
  14. Equivalents to MSVC’s _countof in other compilers?
  15. Why exactly should I not call free() on variables not allocated by malloc()?
  16. Why both clang and gcc only give a warning when there is a space after backslash if C standard says that whitespace is forbidden?
  17. Can’t compile C program on a Mac after upgrade to Mojave
  18. Difference between static memory allocation and dynamic memory allocation
  19. Can I use Intel syntax of x86 assembly with GCC?
  20. Stack allocation, padding, and alignment
  21. Where are constant variables stored in C?
  22. “undefined reference to `pow'” even with math.h and the library link -lm [duplicate]
  23. How Can I debug a C program on Linux?
  24. How to place a variable at a given absolute address in memory (with GCC)
  25. What are the differences between -std=c++11 and -std=gnu++11?
  26. Implementation of nested functions
  27. Is it ok to use “classic” malloc()/free() in Objective-C/iPhone apps?
  28. How can a shared library (.so) call a function that is implemented in its loader code?
  29. How can I include a needed C library using GCC?
  30. How do I compile the asm generated by GCC?

Leave a Comment