Dynamic Memory Allocation in C++

Dynamic Memory Allocation in C++

📘 Overview Dynamic memory allocation creates objects whose lifetimes are controlled independently of the scope that requested them. C++ provides new and delete for explicit management, but standard containers and smart pointers usually provide safer ownership.

🧠 Key Idea Dynamically allocated objects remain alive until their storage is released by the responsible owner. Correct ownership prevents memory leaks, dangling pointers, and repeated deallocation.

⚔️ Core Details: - A new expression obtains storage, initializes an object, and returns a pointer: int* p = new int{42};. - A delete expression destroys an object and releases its storage: delete p;. - Array allocations require matching array deallocation: int* values = new int[count]{}; pairs with delete[] values;. - Ordinary throwing new reports allocation failure by throwing std::bad_alloc. - Deleting an object leaves other pointers to it dangling; accessing the destroyed object through them causes undefined behavior. - RAII ties resource ownership to an object's lifetime; std::unique_ptr, std::shared_ptr, and std::vector release owned resources automatically.

🎯 Why It Matters: - Runtime-sized storage supports collections whose sizes are unknown at compilation. - Explicit ownership allows objects to outlive the functions that create them without returning pointers to destroyed local objects. - Automatic resource management reduces leaks and use-after-free defects across normal returns and exception paths. - Unnecessary allocations add runtime overhead and can reduce cache locality compared with contiguous container storage.

🧠 Quick Recall: - Allocation pairing - Match new with delete and new[] with delete[]; mismatches cause undefined behavior. - Memory leak - Allocated storage remains unreleased after the program loses the means to free it. - Double deletion - Deallocating the same allocation more than once causes undefined behavior. - nullptr - The null pointer value; deleting a null pointer is safe, but nulling one pointer does not fix dangling aliases. - Ownership tools - std::make_unique creates exclusive smart-pointer ownership; std::make_shared creates shared ownership; std::vector manages dynamic arrays.