Stack and Heap in C#

Stack and Heap in C# with Examples

In this article, I am going to discuss Stack and Heap in C# Application with examples. Please read our previous article, where we discussed the Checked and unchecked keywords in C#. As part of this article, first, we will discuss what happens internally when we declare a variable of value types as well as reference types. Then we will move forward and learn two important concepts i.e. stack and heap memory as well as we will talk about value types and reference types.

What happens internally when we declare a variable in .NET Application?

When we declare a variable in a .NET application, it allocates some memory in the RAM. The memory which it allocates in RAM has three things are as follows:

  1. Name of the variable,
  2. The data type of the variable, and
  3. Value of the variable.

For better understanding, please have a look at the following image. Here, we declare a variable of type int and assign a value 101.

What happens internally when we declare a variable in .NET Application?

The above image shows a high-level overview of what happening in the memory. But depending on the data type (i.e. depending on the value type and reference type ), the memory may be allocated either in the stack or in the heap memory.

Understanding Stack and Heap Memory in C#:

There are two types of memory allocation for the variables that we created in the .NET Application i.e. stack memory and heap memory. Let us understand the stack and heap memory with an example. In order to understand stack and heap, please have a look at the following code, and let’s understand what actually happens in the below code internally.

Understanding Stack and Heap Memory in .NET

As you can see in the above image, the SomeMethod having three statements, let’s understand statement by statement how things are executed internally.

Statement1:

When the first statement is executed, the compiler allocates some memory in the stack. The stack memory is responsible for keeping track of the running memory needed in your application. For better understanding, please have a look at the following image.

Stack in .NET Application with Examples

Statement2:

When the second statement is executed, it stacks this memory allocation (memory allocation for variable y) on top of the first memory allocation (memory allocation for variable x). You can think about the stack as a series of plates or dishes put on top of each other. Please have a look at the following diagram for a better understanding.

Stack memory in C#

The Stack Memory allocation and de-allocation in .NET are done using the Last In First Out principle. In other words, we can say that the memory allocation and de-allocation are done only at one end of the memory, i.e., the top of the stack.

Statement3:

In the 3rd statement, we have created an object of SomeClass. When the 3rd statement is executed, it internally creates a pointer on the stack memory and the actual object is stored in a different memory location called Heap memory. The heap memory location does not track running memory. Heap is used for dynamic memory allocation. For better understanding please have a look at the below image.

Heap Memory in .NET Application

Note: The reference pointers are allocated on the stack. The statement, SomeClass cls1 does not allocate any memory for an instance of SomeClass, it only allocates a variable with the name cls1 in the stack and sets its value to null. The time it hits the new keyword, it allocates on the memory in the heap.

What happens when the method completes its execution?

When the three statements are executed, then the control will exist from the method. When it passes the end control i.e. the end curly brace “}”, it will clear all the memory variables which are created on the stack. It will de-allocate the memory in ‘LIFO’ fashion from the stack. For better understanding please have a look at the below image.

What happens to stack and Heap memory when the method complete its execution?

It will not de-allocate the heap memory. Later, the heap memory will be de-allocated by the garbage collector. Now you may have one question in your mind is why two types of memory, can’t we just allocate everything on just one memory type?

Why do we have two types of memory?

As we know, in C#, the primitive data types such as int, double, bool, etc. they just hold a single value. On the other hand, the reference data types or object data types are complex i.e. an object data type or reference data type can have reference to other objects as well as other primitive data types.

So, the reference data type holds references to other multiple values, and each one of them must be stored in memory. Object types need dynamic memory while primitive data types need static memory. Please have a look at the following image for a better understanding.

Why we have two types of memory (Stack and Heap in .NET)?

Value types and reference types in .NET

As we understood the concept of Stack and Heap, Now, let us move forward and understand the concept value types and reference types in detail. The Value types are the types that hold both data and memory in the same location. On the other hand, a reference type is a type that has a pointer that points to the actual memory location.

Understanding Value Type:

Let us understand value type with an example. Please have a look at the following image. As you can see in the image, first we create an integer variable with the name x and then we assign this x integer value to another integer variable whose name is y. In both these memory values are allocated on the stack.

Understanding Value Type in .NET

In .NET, when we assign one integer variable value to another integer variable, then it creates a completely different copy in the stack memory that’s what you can see in the above image. So, if you change one variable value, then the other variable will not be affected. In .NET these kinds of data types are called ‘Value types’. So, bool, byte, char, decimal, double, enum, float, long, sbyte, int, short, ulong, struct, uint, ushort are examples of value types.

Understanding Reference Type in C#:

Let us understand reference type with an example. Please have a look at the following image. Here, first, we create an object i.e. obj1) and then assign this object to another object i.e. obj2. In this case, both reference variables (obj1 and obj2) will point to the same memory location.

Understanding Reference Type in C#

In this case, when you change one of them, the other object is also gets affected. These kinds of data types are termed as ‘Reference types’ in .NET. So, class, interface, object, string, and delegate are the example of Reference Types.

How is the heap memory freed up?

The memory allocation which is done on the stack is gone when the control moves out from the method i.e once the method completes its execution. On the other hand, the memory allocation which is done on the heap needs to be de-allocated by the garbage collector.

When an object stored on the heap is no longer use, that means the object does not have any reference pointing, then the object is eligible for garbage collection. At some point in time, the garbage collector will de-allocate this object from the heap.

In the next article, I am going to discuss Boxing and Unboxing in .NET with examples. Here, in this article, I try to explain Stack and Heap in C# with some examples. I hope you enjoy this article. I would like to have your feedback. Please post your feedback, question, or comments about this article.

6 thoughts on “Stack and Heap in C#”

  1. blank

    I love this site , each and everything is explain very well . All topic are covered by this site no need to go anywhere just read it carefully .

    Thanks to make it

  2. Pingback: Các hiểu biết cơ bản về C# - Trang Chủ

  3. blank

    Nice articles. I am very easy to understand these concepts. Boxing and Unboxing in the .NET concept are missing in the next article. please post this article.

Leave a Reply

Your email address will not be published. Required fields are marked *