Many developers spend much of their career blissfully unaware of garbage collection. A lucky few encounter slow performance or encounter an out of memory exception. Those lucky few who have the opportunity to investigate the cause may discover a world overlooked by much of the .Net community. Generally, there is nothing wrong with overlooking this area; after all the garbage collector does a very good job of handling managed memory. However, there are some situations where the programmer is dealing with unmanaged memory or the algorithm creates a great deal of work for the garbage collector causing performance problems. In this session I will discuss several situations that can cause problems for the Garbage collector and how avoid these problems. Lastly I will introduce some tools and techniques for tracking down these problems in an application.