Are memory leaks “undefined behavior” class problem in C++?

by

Memory leaks.

There is no undefined behavior. It is perfectly legal to leak memory.

Undefined behavior: is actions the standard specifically does not want to define and leaves upto the implementation so that it is flexible to perform certain types of optimizations without breaking the standard.

Memory management is well defined.
If you dynamically allocate memory and don’t release it. Then the memory remains the property of the application to manage as it sees fit. The fact that you have lost all references to that portion of memory is neither here nor there.

Of course if you continue to leak then you will eventually run out of available memory and the application will start to throw bad_alloc exceptions. But that is another issue.

More Related Contents:

  1. Avoid memory leaks in C++ Pointers [closed]
  2. How could pairing new[] with delete possibly lead to memory leak only?
  3. What do I need to do before deleting elements in a vector of pointers to dynamically allocated objects?
  4. Implementing a std::vector like container without undefined behavior
  5. new() without delete() is Undefined Behavior or merely Memory Leak? [duplicate]
  6. dynamically allocated memory after program termination
  7. C++ is it necessary to delete dynamically allocated objects at the end of the main scope?
  8. C++ delete does not free all memory (Windows)
  9. Why should C++ programmers minimize use of ‘new’?
  10. What uses are there for “placement new”?
  11. Accessing inactive union member and undefined behavior?
  12. Has C++ standard changed with respect to the use of indeterminate values and undefined behavior in C++14?
  13. Dynamically allocating an array of objects
  14. Why does left shift operation invoke Undefined Behaviour when the left side operand has negative value?
  15. C++, Free-Store vs Heap
  16. How to get memory usage under Windows in C++
  17. Check if a pointer points to allocated memory on the heap
  18. How do we explain the result of the expression (++x)+(++x)+(++x)?
  19. Virtual destructor and undefined behavior
  20. Reason why not to have a DELETE macro for C++
  21. Why, really, deleting an incomplete type is undefined behaviour?
  22. Arithmetic right shift gives bogus result?
  23. What is “bit padding” or “padding bits” exactly?
  24. Why is the phrase: “undefined behavior means the compiler can do anything it wants” true?
  25. Are pointer variables just integers with some operators or are they “symbolic”?
  26. The behaviour of floating point division by zero
  27. Why doesn’t vector::clear remove elements from a vector?
  28. How to alloc a executable memory buffer?
  29. new, delete ,malloc & free
  30. Should objects delete themselves in C++?

Leave a Comment