Thanks to the garbage collector, we as .NET developers rarely have to deal with memory leaks. But when we do, it can be quite difficult to find and solve them. First of all, it is often a matter of recognizing the type of problem. Is it actually in the managed memory? If so, which part of our coding or dependencies is responsible?

In this talk, we will look at different types of memory leaks. How they occur, which tools we can use to detect them and how we can fix them. Along the way, we will also learn how the garbage collector works and why sometimes something looks like we have a memory leak that actually isn't one.