Is there a reason to call delete in C++ when a program is exiting anyway?

by

It is important to explicitly call delete because you may have some code in the destructor that you want to execute. Like maybe writing some data to a log file. If you let the OS free your memory for you, your code in your destructor will not be executed.

Most operating systems will deallocate the memory when your program ends. But it is good practice to deallocate it yourself and like I said above the OS won’t call your destructor.

As for calling delete in general, yes you always want to call delete, or else you will have a memory leak in your program, which will lead to new allocations failing.

More Related Contents:

  1. C++ – destructors [closed]
  2. Why should C++ programmers minimize use of ‘new’?
  3. Proper stack and heap usage in C++?
  4. What is the difference between “new” and “malloc” and “calloc” in C++? [duplicate]
  5. How is heap and stack memories managed, implemented, allocated?
  6. Does this type of memory get allocated on the heap or the stack?
  7. Class members and explicit stack/heap allocation
  8. Why do we even need the “delete[]” operator?
  9. C++ delete does not free all memory (Windows)
  10. Avoid memory leaks in C++ Pointers [closed]
  11. Calling delete on variable allocated on the stack
  12. delete vs delete[] [duplicate]
  13. How to get memory usage at runtime using C++?
  14. When vectors are allocated, do they use memory on the heap or the stack?
  15. Why doesn’t delete set the pointer to NULL?
  16. Smart pointers: who owns the object? [closed]
  17. Why is stack memory size so limited?
  18. Is it possible to create a function dynamically, during runtime in C++?
  19. How do you determine the size of an object in C++?
  20. Initial capacity of vector in C++
  21. Why would you ever want to allocate memory on the heap rather than the stack? [duplicate]
  22. Why is there no reallocation functionality in C++ allocators?
  23. Are there stackless or heapless implementation of C++?
  24. Is it safe to realloc memory allocated with new?
  25. Implementing a std::vector like container without undefined behavior
  26. Call destructor and then constructor (resetting an object)
  27. Memory allocation and deallocation across dll boundaries
  28. How to track memory allocations in C++ (especially new/delete)
  29. What’s the advantage of using std::allocator instead of new in C++?
  30. Memory-efficient C++ strings (interning, ropes, copy-on-write, etc) [closed]

Leave a Comment