pythonic metaphor
Reputation: 10556
Operator new and bad_alloc on linux
On Linux, malloc doesn't necessarily return a null pointer if you're out of memory. You might get back a pointer and then have the OOM killer start eating processes if you're really out of memory. Is the same true for c++'s operator new or will you get the bad_alloc exception?
Upvotes: 3
Views: 1255
Answers (2)
caf
Reputation: 239171
It's a kernel function rather than a language function - and you can control it with the vm.overcommit_memory and vm.overcommit_ratio sysctls.
They're visible in the proc filesystem at /proc/sys/vm/overcommit_memory and /proc/sys/vm/overcommit_ratio.
Upvotes: 7
Related Questions
- New throws bad_alloc despite <new> header not being defined?
- operator new doesn't return 0 when running out of memory
- how to cause bad_alloc
- Best way to safely call new on this trivial example?
- understanding std::bad_alloc in C++ class
- New operator crash
- C++ bad_alloc caused by new?
- C++ memory allocation errors without use of new
- Terminate with bad_alloc exception, but no "new" in stack trace
- problems with operator new when allocating arrays