Skip to main content
This is lesson 3 of 7 in this module Course 57% complete
Prev Next Skip

Heap Compaction and Object References

Premium Content

Sign in with your account or sign up to access this lesson.

Sign In Sign Up

We explain why heap compaction requires that references cannot be raw memory addresses, leading to .NET's double-pointer design where every reference is a pointer-to-a-pointer managed by the garbage collector. The lesson also covers the unsafe keyword and the fixed statement which temporarily pins objects on the heap so that native pointers can be used safely.

Previous Next
Previous Module Array Performance Optimizations
This Module The .NET Garbage Collector
Introducing Garbage Collection (GC)
Introducing Garbage Collection (GC)
Mark and Sweep GC
Mark and Sweep GC
Heap Compaction and Object References
Heap Compaction and Object References
Generational Garbage Collection
Generational Garbage Collection
The Small and Large Object Heaps
The Small and Large Object Heaps
GC Performance and Assumptions
GC Performance and Assumptions
GC Memory Layout Strategies
GC Memory Layout Strategies
Next Module Memory Performance Optimizations