Can I rely on malloc returning NULL?

by

Quoting Linux manuals:

By default, Linux follows an optimistic memory allocation strategy. This means that when malloc() returns non-NULL there is no
guarantee that
the memory really is available. This is a really bad bug. In case it turns out that the system is out of memory, one or more
processes will be
killed by the infamous OOM killer. In case Linux is employed under circumstances where it would be less desirable to suddenly lose
some randomly
picked processes, and moreover the kernel version is sufficiently recent, one can switch off this overcommitting behavior
using a command like:

# echo 2 > /proc/sys/vm/overcommit_memory

You ought to check for NULL return, especially on 32-bit systems, as the process address space could be exhausted far before the RAM: on 32-bit Linux for example, user processes might have usable address space of 2G – 3G as opposed to over 4G of total RAM. On 64-bit systems it might be useless to check the malloc return code, but might be considered good practice anyway, and it does make your program more portable. And, remember, dereferencing the null pointer kills your process certainly; some swapping might not hurt much compared to that.

If malloc happens to return NULL when one tries to allocate only a small amount of memory, then one must be cautious when trying to recover from the error condition as any subsequent malloc can fail too, until enough memory is available.

The default C++ operator new is often a wrapper over the same allocation mechanisms employed by malloc().

More Related Contents:

  1. How do free and malloc work in C?
  2. How is malloc() implemented internally? [duplicate]
  3. malloc(sizeof(int)) vs malloc(sizeof(int *)) vs (int *)malloc(sizeof(int))
  4. If free() knows the length of my array, why can’t I ask for it in my own code?
  5. Should I check if malloc() was successful?
  6. Malloc vs custom allocator: Malloc has a lot of overhead. Why?
  7. Why exactly should I not call free() on variables not allocated by malloc()?
  8. Why this program is crashing?
  9. Getting a stack overflow exception when declaring a large array
  10. Determine size of dynamically allocated memory in C
  11. Difference between static memory allocation and dynamic memory allocation
  12. What’s the point of malloc(0)?
  13. “register” keyword in C?
  14. Overriding ‘malloc’ using the LD_PRELOAD mechanism
  15. Using malloc for allocation of multi-dimensional arrays with different row lengths
  16. Why is malloc not “using up” the memory on my computer?
  17. Returning local data from functions in C and C++ via pointer
  18. Writing to pointer out of bounds after malloc() not causing error
  19. Pointer address in a C multidimensional array
  20. Incompatible implicit declaration of built-in function ‘malloc’
  21. C Warning: Function returns address of local variable
  22. dynamic allocating array of arrays in C
  23. Why do I get a warning every time I use malloc?
  24. An alternative for the deprecated __malloc_hook functionality of glibc
  25. Reading Other Process’ Memory in OS X?
  26. Code for malloc and free
  27. Is typecast required in malloc? [duplicate]
  28. C Memory Management
  29. Where do malloc() and free() store allocated sizes and addresses?
  30. How to check heap size for a process on Linux

Leave a Comment