Under the Hood of .NET Memory Management - Simple Talk

Chapter 6: A Few More Advanced Topics
}
if (stringPointer != IntPtr.Zero )
Marshal.FreeHGlobal(stringPointer );
Listing 6.9: Explicitly free unmanaged memory that has been allocated.
In this example, you would effectively leak 32 bytes of data every time this method is
called, in addition to however many bytes were needed to hold the stringValue. This
could easily become a memory flood instead of just a leak.
As a rule, I'd recommend that you isolate code that allocates or uses marshaled memory
to a central location. This type of logic should not be spread throughout your code
base, but rather isolated to proxy classes providing access to the desired unmanaged
functionality. Additionally, this code should be routinely monitored to ensure that all best
practices are consistently followed, because these code constructs are easily abused.
Conclusion
The world of software advances at an amazing pace. Fortunately for us, the .NET
framework advances at an equally amazing pace. As hardware advancements have made
64-bit architectures more prevalent, the framework kept pace, to provide excellent
support for 64-bit programs. Future versions will assuredly continue to keep pace,
providing ever-improving support for parallel and asynchronous programming to take
advantage of similar hardware advances in multicore technology.
The GC is a pillar of the .NET framework, separating it from all other development
platforms; indeed the success of the framework is directly tied to how effective the
GC is. The GC's effectiveness is at least partly a function of how well it stays out of the
way of developers, and avoids being overtly noticed by the user. Each new version of
.NET has set out to make the GC less and less intrusive, yet more effective at managing
memory – a powerful combination.
195