Will malloc implementations return free-ed memory back to the system?

by

The following analysis applies only to glibc (based on the ptmalloc2 algorithm).
There are certain options that seem helpful to return the freed memory back to the system:

  1. mallopt() (defined in malloc.h) does provide an option to set the trim threshold value using one of the parameter option M_TRIM_THRESHOLD, this indicates the minimum amount of free memory (in bytes) allowed at the top of the data segment. If the amount falls below this threshold, glibc invokes brk() to give back memory to the kernel.

    The default value of M_TRIM_THRESHOLD in Linux is set to 128K, setting a smaller value might save space.

    The same behavior could be achieved by setting trim threshold value in the environment variable MALLOC_TRIM_THRESHOLD_, with no source changes absolutely.

    However, preliminary test programs run using M_TRIM_THRESHOLD has shown that even though the memory allocated by malloc does return to the system, the remaining portion of the actual chunk of memory (the arena) initially requested via brk() tends to be retained.

  2. It is possible to trim the memory arena and give any unused memory back to the system by calling malloc_trim(pad) (defined in malloc.h). This function resizes the data segment, leaving at least pad bytes at the end of it and failing if less than one page worth of bytes can be freed. Segment size is always a multiple of one page, which is 4,096 bytes on i386.

    The implementation of this modified behavior of free() using malloc_trim could be done using the malloc hook functionality. This would not require any source code changes to the core glibc library.

  3. Using madvise() system call inside the free implementation of glibc.

More Related Contents:

  1. How do malloc() and free() work?
  2. What REALLY happens when you don’t free after malloc before program termination?
  3. How do free and malloc work in C?
  4. Setting variable to NULL after free
  5. Should I free memory before exit?
  6. free char*: invalid next size (fast) [duplicate]
  7. C – Accessing data AFTER memory has been free()ed?
  8. malloc implementation?
  9. If free() knows the length of my array, why can’t I ask for it in my own code?
  10. Why do I get different results when I dereference a pointer after freeing it?
  11. C: Correctly freeing memory of a multi-dimensional array
  12. An alternative for the deprecated __malloc_hook functionality of glibc
  13. Is freeing allocated memory needed when exiting a program in C
  14. Problem usage memory in C
  15. Why exactly should I not call free() on variables not allocated by malloc()?
  16. How are we able to access the pointer after deallocating the memory?
  17. Code for malloc and free
  18. new, delete ,malloc & free
  19. convert malloc to new c++ for struct
  20. When and why to use malloc?
  21. What is the difference between “new” and “malloc” and “calloc” in C++? [duplicate]
  22. How to upgrade glibc from version 2.12 to 2.14 on CentOS?
  23. How big can a memory-mapped file be?
  24. How big can a malloc be in C?
  25. malloc: *** error: incorrect checksum for freed object – object was probably modified after being freed
  26. dynamically allocated memory after program termination
  27. Sorting list of string with specific locale in python
  28. Can you allocate a very large single chunk of memory ( > 4GB ) in c or c++?
  29. A different way to malloc a 2D array?
  30. What is C++ version of realloc(), to allocate the new buffer and copy the contents from the old one?

Leave a Comment