C++ is it necessary to delete dynamically allocated objects at the end of the main scope?

by

Most of the modern OS always reclaim back all memory they allocated to a program(process).
The OS doesn’t really understand if your program leaked memory it merely takes back what it allocatted.

But there are bigger issues at hand than just the memory loss:

Note that if the destructor of the object whos delete needs to be called performs some non-trivial operation and your program depends on the side effects produced by it then your program falls prey to Undefined Behavior[Ref 1]. Once that happens all bets are off and your program may show any beahvior.

Also, An OS usually reclaims the allocated memory but not the other resources, So you might leak those resources indirectly. This may include operations dealing with file descriptors or state of the program itself etc.

Hence, it is a good practice to always deallocate all your allocations by calling delete or delete [] before exiting your program.

[Ref 1]C++03 Standard 3.8 Para 4:

“….if there is no explicit call to the destructor or if a delete-expression (5.3.5) is not used to release the storage, the destructor shall not be implicitly called and any program that depends on the side effects produced by the destructor has undefined behavior.”

More Related Contents:

  1. Avoid memory leaks in C++ Pointers [closed]
  2. Are memory leaks “undefined behavior” class problem in C++?
  3. What do I need to do before deleting elements in a vector of pointers to dynamically allocated objects?
  4. dynamically allocated memory after program termination
  5. C++ delete does not free all memory (Windows)
  6. C++ Memory Leak Using char *
  7. Why should C++ programmers minimize use of ‘new’?
  8. What uses are there for “placement new”?
  9. In what cases do I use malloc and/or new?
  10. delete vs delete[] operators in C++
  11. Is it safe to delete a NULL pointer?
  12. Operator new initializes memory to zero
  13. What strategies and tools are useful for finding memory leaks in .NET?
  14. Large Object Heap Fragmentation
  15. C++, Free-Store vs Heap
  16. .NET Memory issues loading ~40 images, memory not reclaimed, potentially due to LOH fragmentation
  17. How do you detect/avoid Memory leaks in your (Unmanaged) code? [closed]
  18. Allocating more memory than there exists using malloc
  19. How can I get the size of a memory block allocated using malloc()? [duplicate]
  20. std::vector and contiguous memory of multidimensional arrays
  21. Pointer-to-pointer dynamic two-dimensional array
  22. Can I pass std::string to a DLL?
  23. Is it safe to realloc memory allocated with new?
  24. valgrind memory leak errors when using pthread_create
  25. new() without delete() is Undefined Behavior or merely Memory Leak? [duplicate]
  26. In Visual Studio, `thread_local` variables’ destructor not called when used with std::async, is this a bug?
  27. How does delete work? [duplicate]
  28. How to check memory allocation failures with new operator?
  29. OpenSSL::SSL_library_init() memory leak
  30. Memory-efficient C++ strings (interning, ropes, copy-on-write, etc) [closed]

Leave a Comment