By mswatcher
via geekswithblogs.net
Submitted: Jan 28 2013 / 10:35
It’s pretty well documented that one of the most common ways in which a .NET application can “leak” memory stems failing to unsubscribe from events when the subscription is no longer needed. This answer to a Stack Overflow question on memory leaks in C# describes the issue very succinctly:
Tweet
SaveShareSend
Tags: .net, frameworks, other languages
Add your comment
