Sharing this great memory leak article on MSDN (Though I myself have to read it)
http://msdn.microsoft.com/en-us/library/ee658248.aspx
Namaste (Greetings)
| Anugrah Atreya
Subscribe to:
Post Comments (Atom)
With this blog I try to share the solutions of real time problems I have faced in different software solutions. Most of these are related to C#.NET and interation of C#.NEt with C++.NET
Posts
2 comments:
Detection of Leak:
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.
Avoidance of Leak:
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.
womens health
Hey Sara, Thanks for your comments. I hope you find more useful things here on this blog of mine.
Anugrah
Post a Comment