.NET Memory management is an impressive and comprehensive system, but it's not flawless, and can be anti-intuitive. As a result, there are a few common misconceptions which need to be dispelled before you can really get the most out of the .NET framework.
.NET Memory management is an impressively complex process, and most of the time it works pretty well. However, it’s not flawless, and neither are we developers, so memory management problems are still something that a skilled developer should be prepared for. And while it’s possible to have useful information about .NET memory management and write better code without fully understanding the black box inside the framework, there are a few common misconceptions which need to be dispelled before you can really get started:
- A garbage collector collects garbage
- Doing lots of gen0 collections is bad
- Performance counters are great for understanding what is happening
- .NET doesn’t leak memory
- All objects are treated the same
Trackback:http://www.simple-talk.com/dotnet/performance/the-top-5-.net-memory-management-misconceptions/?utm_source=simpletalk&utm_medium=email-main&utm_content=rickyleeks-20110808&utm_campaign=.NET