Скачать или смотреть Understanding Heap Memory Allocation with the new Operator in C+ +

Learn how memory allocation works using the `new` operator in C+ + , specifically when dealing with arrays and pointers.
---
This video is based on the question https://stackoverflow.com/q/64687657/ asked by the user 'dimm' ( https://stackoverflow.com/u/12087158/ ) and on the answer https://stackoverflow.com/a/64687694/ provided by the user 'Bathsheba' ( https://stackoverflow.com/u/2380830/ ) at 'Stack Overflow' website. Thanks to these great users and Stackexchange community for their contributions.

Visit these links for original content and any more details, such as alternate solutions, latest updates/developments on topic, comments, revision history etc. For example, the original title of the Question was: How much memory is allocated in heap using new operator?

Also, Content (except music) licensed under CC BY-SA https://meta.stackexchange.com/help/l...
The original Question post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license, and the original Answer post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license.

If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com.
---
Understanding Heap Memory Allocation with the new Operator in C+ +

In C+ + , managing memory is a critical skill, especially when working with dynamic data structures. One common point of confusion for many developers is how memory is allocated on the heap using the new operator. Today, we’re going to clarify this concept, addressing a common question about memory allocation for arrays and pointers.

The Question

When you allocate memory on the heap in C+ + using the new operator, it can be confusing to determine exactly how much memory is allocated. A common example is:

[[See Video to Reveal this Text or Code Snippet]]

In this code snippet, how much memory is being allocated? Is it simply 40 bytes for the 10 integers, or is there additional allocation for the pointer? Where does this memory reside – on the stack or the heap?

The Breakdown: Memory Allocation

Memory for the Integers

First, let's talk about the memory allocated for the integers. The line:

[[See Video to Reveal this Text or Code Snippet]]

allocates memory for 10 integers on the heap. Each int typically occupies 4 bytes of memory on most modern architectures. Therefore, the total memory allocated is:

10 integers × 4 bytes each = 40 bytes.

However, it’s essential to note that the C+ + runtime might allocate additional memory for bookkeeping purposes, but that's not visible to the programmer in a straightforward way.

Memory for the Pointer

Next, we need to consider the pointer itself. The pointer ptr holds the address of the first element of the allocated integer array. This pointer has a storage duration that is automatic, which means:

It is allocated on the stack when the function main() is called.

Typically, on a modern desktop system, this pointer would occupy 8 bytes (for a 64-bit architecture) or 4 bytes (for a 32-bit architecture).

Summary of Memory Allocation

To summarize the memory allocation in the example:

Heap Memory:

40 bytes allocated for 10 integers (this is where the array data is stored).

Stack Memory:

8 bytes allocated for the ptr pointer (this is where the pointer itself is stored).

Hence, the total memory allocation for the whole line is 40 bytes on the heap and 8 bytes on the stack.

Key Takeaways

Using the new operator in C+ + allocates memory on the heap.

The memory required for multiple ints can be calculated as number of elements × sizeof(int).

Pointers are stored on the stack, while the data they point to is on the heap.

Always remember to deallocate memory using delete[] ptr; to prevent memory leaks.

In conclusion, understanding how memory allocation works in C+ + is crucial for efficient programming. The new operator provides powerful dynamic memory capabilities, but with that power comes the responsibility of managing that memory effectively. Happy coding!