Anatomy of a “Memory Leak”

by

The best explanation I’ve seen is in Chapter 7 of the free Foundations of Programming e-book.

Basically, in .NET a memory leak occurs when referenced objects are rooted and thus cannot be garbage collected. This occurs accidentally when you hold on to references beyond the intended scope.

You’ll know that you have leaks when you start getting OutOfMemoryExceptions or your memory usage goes up beyond what you’d expect (PerfMon has nice memory counters).

Understanding .NET‘s memory model is your best way of avoiding it. Specifically, understanding how the garbage collector works and how references work — again, I refer you to chapter 7 of the e-book. Also, be mindful of common pitfalls, probably the most common being events. If object A is registered to an event on object B, then object A will stick around until object B disappears because B holds a reference to A. The solution is to unregister your events when you’re done.

Of course, a good memory profile will let you see your object graphs and explore the nesting/referencing of your objects to see where references are coming from and what root object is responsible (red-gate ants profile, JetBrains dotMemory, memprofiler are really good choices, or you can use the text-only WinDbg and SOS, but I’d strongly recommend a commercial/visual product unless you’re a real guru).

I believe unmanaged code is subject to its typical memory leaks, except that shared references are managed by the garbage collector. I could be wrong about this last point.

More Related Contents:

  1. Clean up Excel Interop Objects with IDisposable
  2. Which method performs better: .Any() vs .Count() > 0?
  3. HashSet vs. List performance
  4. Why are multi-dimensional arrays in .NET slower than normal arrays?
  5. Performance of Arrays vs. Lists
  6. What’s so wrong about using GC.Collect()?
  7. String.Join vs. StringBuilder: which is faster?
  8. How to measure code performance in .NET?
  9. Circular References Cause Memory Leak?
  10. HashSet versus Dictionary w.r.t searching time to find if an item exists
  11. How to get around the memory leak in the .NET Webbrowser control?
  12. Why seal a class?
  13. .NET LINQ query syntax vs method chain
  14. Why is the first WCF client call slow?
  15. Is datareader quicker than dataset when populating a datatable?
  16. Can you get a Func (or similar) from a MethodInfo object?
  17. What are alternatives to generic collections for COM Interop?
  18. System.IO.FileSystemWatcher to monitor a network-server folder – Performance considerations
  19. Optimum file buffer read size?
  20. How do I improve ASP.NET MVC application performance?
  21. Which is faster: clear collection or instantiate new
  22. How do I use a dump file to diagnose a memory leak?
  23. Does .NET assembly size affect performance?
  24. Memory leaks in .NET [closed]
  25. IIS: web applications warmup
  26. “Register for COM Interop” vs “Make assembly COM visible”
  27. Entity Framework Find vs. Where
  28. Performance: XDocument versus XmlDocument
  29. Opening XPS document in .Net causes a memory leak
  30. WPF slow to start on x64 in .NET Framework 4.0

Leave a Comment