Destructor being called twice when being explicitly invoked

by

It happens because you told it to happen. The destructor for an automatic variable is always called when the variable goes out of scope. You also called it. That’s two calls total.

Calling an object’s destructor does not signal to C++ not to call it again, since in normal execution there is no need to keep track.

The solution is to never manually call your destructor.

More Related Contents:

  1. If you shouldn’t throw exceptions in a destructor, how do you handle errors in it?
  2. C++: Life span of temporary arguments?
  3. Dynamically allocating an array of objects
  4. shared_ptr magic :)
  5. Why do we need a pure virtual destructor in C++?
  6. Object destruction in C++
  7. Is calling destructor manually always a sign of bad design?
  8. calling destructor explicitly
  9. Does C++ call destructors for global and class static variables?
  10. What is the use of having destructor as private?
  11. When is a C++ destructor called?
  12. When is an object “out of scope”?
  13. Does std::list::remove method call destructor of each removed element?
  14. Forward declaration with unique_ptr? [duplicate]
  15. Is it possible to delete a non-new object?
  16. Does delete on a pointer to a subclass call the base class destructor?
  17. Why don’t STL containers have virtual destructors?
  18. Is a destructor called when an object goes out of scope?
  19. Why do un-named C++ objects destruct before the scope block ends?
  20. Will exit() or an exception prevent an end-of-scope destructor from being called?
  21. How to add constructors/destructors to an unnamed class?
  22. Why, really, deleting an incomplete type is undefined behaviour?
  23. Creating an object: with or without `new` [duplicate]
  24. How is it possible (if it is) to implement shared_ptr without requiring polymorphic classes to have virtual destructor?
  25. problems with Move constructor and Move overloaded assignment operator?
  26. Lifetime of object is over before destructor is called?
  27. Under what circumstances are C++ destructors not going to be called?
  28. Observable behavior and undefined behavior — What happens if I don’t call a destructor?
  29. Is the whole object freed with a non-virtual destructor and a Base class pointer?
  30. C++ Constructor/Destructor inheritance

Leave a Comment