Calling delete on variable allocated on the stack

by

No, it is not safe to call delete on a stack-allocated variable. You should only call delete on things created by new.

  • For each malloc or calloc, there should be exactly one free.
  • For each new there should be exactly one delete.
  • For each new[] there should be exactly one delete[].
  • For each stack allocation, there should be no explicit freeing or deletion. The destructor is called automatically, where applicable.

In general, you cannot mix and match any of these, e.g. no free-ing or delete[]-ing a new object. Doing so results in undefined behavior.

More Related Contents:

  1. Stack, Static, and Heap in C++
  2. Which is faster: Stack allocation or Heap allocation
  3. Proper stack and heap usage in C++?
  4. Does this type of memory get allocated on the heap or the stack?
  5. How to prevent an object being created on the heap?
  6. Are there differences between pointers to object stored on stack and heap? [closed]
  7. Is delete[] equal to delete?
  8. Why are the terms “automatic” and “dynamic” preferred over the terms “stack” and “heap” in C++ memory management?
  9. How should I write ISO C++ Standard conformant custom new and delete operators?
  10. Object creation on the stack/heap?
  11. C++ delete vector, objects, free memory
  12. Is there any reason to check for a NULL pointer before deleting?
  13. What is the difference between “new” and “malloc” and “calloc” in C++? [duplicate]
  14. When and how to use GCC’s stack protection feature?
  15. Why is it undefined behavior to delete[] an array of derived objects via a base pointer?
  16. Double free or corruption after queue::push
  17. Does delete on a pointer to a subclass call the base class destructor?
  18. Why not use pointers for everything in C++?
  19. What happens when you deallocate a pointer twice or more in C++?
  20. What is the behavior of “delete” with stack objects? [duplicate]
  21. When to use new and delete
  22. Does std::stack expose iterators?
  23. Critique my non-intrusive heap debugger
  24. How is heap and stack memories managed, implemented, allocated?
  25. Understanding stack frame of function call in C/C++? [closed]
  26. Is accessing data in the heap faster than from the stack?
  27. Weird MSC 8.0 error: “The value of ESP was not properly saved across a function call…”
  28. What’s the advantage of using std::allocator instead of new in C++?
  29. C++ delete does not free all memory (Windows)
  30. Is the whole object freed with a non-virtual destructor and a Base class pointer?

Leave a Comment