Linux optimistic malloc: will new always throw when out of memory?

by

It depends; you can configure the kernel’s overcommit settings using vm.overcommit_memory.

Herb Sutter discussed a few years ago how this behavior is actually nonconforming to the C++ standard:

“On some operating systems, including specifically Linux, memory allocation always succeeds. Full stop. How can allocation always succeed, even when the requested memory really isn’t available? The reason is that the allocation itself merely records a request for the memory; under the covers, the (physical or virtual) memory is not actually committed to the requesting process, with real backing store, until the memory is actually used.

“Note that, if new uses the operating system’s facilities directly, then new will always succeed but any later innocent code like buf[100] = ‘c’; can throw or fail or halt. From a Standard C++ point of view, both effects are nonconforming, because the C++ standard requires that if new can’t commit enough memory it must fail (this doesn’t), and that code like buf[100] = ‘c’ shouldn’t throw an exception or otherwise fail (this might).”

More Related Contents:

  1. How to get memory usage at runtime using C++?
  2. Allocating more memory than there exists using malloc
  3. Can a local variable’s memory be accessed outside its scope?
  4. C++ IDE for Linux? [closed]
  5. Array placement-new requires unspecified overhead in the buffer?
  6. Is it safe to delete a void pointer?
  7. Proper stack and heap usage in C++?
  8. How to initialise memory with new operator in C++?
  9. Compiling multithread code with g++
  10. Using kbhit() and getch() on Linux
  11. 64 bit ntohl() in C++?
  12. How to increase thread priority in pthreads?
  13. How to check what shared libraries are loaded at run time for a given process?
  14. C++: Safe to use longjmp and setjmp?
  15. How to get a stack trace for C++ using gcc with line number information?
  16. Child process receives parent’s SIGINT
  17. linux perf: how to interpret and find hotspots
  18. Linking problems due to symbols with abi::cxx11?
  19. track C++ memory allocations
  20. How to name a thread in Linux? [duplicate]
  21. How to deal with bad_alloc in C++?
  22. dynamically allocated memory after program termination
  23. Inconsistent strcmp() return value when passing strings as pointers or as literals
  24. How do you determine the amount of Linux system RAM in C++?
  25. How to check if a file has been opened by another application in C++?
  26. How to fix: /usr/lib/libstdc++.so.6: version `GLIBCXX_3.4.15′ not found
  27. version `CXXABI_1.3.8′ not found (required by …) [duplicate]
  28. Check keypress in C++ on Linux
  29. How to get the username in C/C++ in Linux?
  30. How to assert if a std::mutex is locked?

Leave a Comment