Stack vs heap mental model in C Sharp (C#) - Visual Side-by-Side Comparison

Concept Flow - Stack vs heap mental model

Start: Program runs

↓

Function call: push stack frame

↓

Allocate local variables on stack

↓

If new object created

↓

Allocate object on heap

↓

Store reference on stack

No↓

Function returns: pop stack frame

↓

Heap objects remain until GC cleans

↓

End

This flow shows how function calls create stack frames with local variables, while objects are allocated on the heap with references stored on the stack.

Execution Sample

C Sharp (C#)

void Foo() {
  int x = 10;
  Person p = new Person();
  p.Name = "Alice";
}

Foo();

This code calls Foo, which stores an int on the stack and creates a Person object on the heap with a reference on the stack.

Execution Table

Step	Action	Stack State	Heap State	Notes
1	Call Foo()	Push Foo stack frame	Empty	Stack frame for Foo created
2	int x = 10;	x=10	Empty	Local int stored on stack
3	Person p = new Person();	x=10, p=ref1	Object Person#1 allocated	Person object created on heap, reference stored in p
4	p.Name = "Alice";	x=10, p=ref1	Person#1.Name = "Alice"	Object field set on heap
5	Return from Foo()	Pop Foo stack frame	Person#1 remains	Stack frame removed, heap object still exists
6	End	Empty	Person#1 remains until GC	Heap object persists until garbage collected

💡 Function returns, stack frame is popped, heap objects remain until garbage collection

Variable Tracker

Variable	Start	After Step 2	After Step 3	After Step 4	After Step 5	Final
x	undefined	10	10	10	undefined	undefined
p	undefined	undefined	ref1	ref1	undefined	undefined
Heap Person#1	none	none	allocated	Name="Alice"	allocated	allocated

Key Moments - 3 Insights

Why does the local variable 'p' store a reference and not the actual object?

Because objects are stored on the heap due to their dynamic size and lifetime, the stack only holds a reference (pointer) to that heap object, as shown in execution_table step 3.

What happens to the heap object after the function returns?

The stack frame is popped and local variables are removed, but the heap object remains until garbage collection, as seen in execution_table steps 5 and 6.

Why are value types like 'int x' stored on the stack?

Value types have fixed size and short lifetime tied to the function call, so they are stored directly on the stack for fast access, as shown in execution_table step 2.

Visual Quiz - 3 Questions

Look at the execution table at step 3. What does variable 'p' hold?

A Null

B A reference to the Person object on the heap

C The actual Person object data

D An integer value

💡 Hint

Check the 'Stack State' and 'Heap State' columns at step 3 in the execution_table.

At which step does the stack frame for Foo get removed?

A Step 5

B Step 2

C Step 4

D Step 6

💡 Hint

Look for 'Pop Foo stack frame' in the 'Action' column of the execution_table.

If 'p' was a value type instead of a reference type, how would the stack state change at step 3?

A 'p' would be null

B 'p' would hold a reference to heap object

C 'p' would hold the actual object data on the stack

D Heap would have no objects

💡 Hint

Refer to variable_tracker and key_moments about value types stored on stack.

Concept Snapshot

Stack vs Heap Mental Model in C#:
- Stack stores local variables and function call info.
- Heap stores objects created with 'new'.
- Stack variables hold values or references.
- Heap objects live beyond function calls until GC.
- Stack is fast and short-lived; heap is slower and long-lived.

Full Transcript

When a C# program runs and calls a function like Foo, a stack frame is created to hold local variables such as integers and references. Value types like int are stored directly on the stack. When the code creates a new object with 'new', the object is allocated on the heap, and the stack stores a reference to it. The heap object can have fields, like Name, which are stored inside the heap. When the function returns, the stack frame is removed, so local variables disappear, but the heap object remains until garbage collection. This model helps understand memory management and variable lifetimes in C#.