Developers using .NET usually will track memory leakage as a low priority task, as the public language runtime will be responsible for garbage collection. However, there are very few developers aware that things are, the life of the object and their size and other objects have been instantiated. Depending on a specific environment, these combinations can have a negative impact on performance, especially within the survival of the application. This article uses the .Net Profiler API to view memory usage and understand garbage collection. At the same time, it also built an example application used to demonstrate these principles.
Click here to read the full story
