tag:blogger.com,1999:blog-4256538220587857609.post3139326132978106752..comments2014-04-01T07:02:35.174-07:00Comments on Explore C# and C++ Programming Tips and Tricks: Detect and avoid memory leaks in .NETAnugrah Ahttp://www.blogger.com/profile/03242166038964647046noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-4256538220587857609.post-67029049488412781402009-11-19T22:16:40.675-08:002009-11-19T22:16:40.675-08:00Hey Sara, Thanks for your comments. I hope you fi...Hey Sara, Thanks for your comments. I hope you find more useful things here on this blog of mine.<br /><br />AnugrahAnugrah Ahttps://www.blogger.com/profile/03242166038964647046noreply@blogger.comtag:blogger.com,1999:blog-4256538220587857609.post-9160561678269617912009-11-17T04:15:07.823-08:002009-11-17T04:15:07.823-08:00Detection of Leak:
Even a little leak can bring do...Detection of Leak:<br />Even a little leak can bring down the system if it occurs many times. This is similar to what happens with leaking water. A drop of water is not a big issue. But drop by drop, a leak can become a major problem. As I will explain later, a single insignificant object can maintain a whole graph of heavy objects in memory. <br /><br />Avoidance of Leak:<br />An object that creates another object is responsible for disposing it. Of course, this is not the case if the creator is a factory. The reverse: an object that receives a reference to another object is not responsible for disposing it. In fact, this really depends on the situation. In any case, what's important to keep in mind is who owns an object.<br /><br /><a href="http://www.vitabits.co.uk/womens-health" rel="nofollow">womens health</a>Sara Reidhttps://www.blogger.com/profile/18373862159812719999noreply@blogger.com