Memory leaks in .NET [closed]

Answer 1

To prevent .NET memory leaks:

1) Employ the 'using' construct (or 'try-finally construct) whenever an object with 'IDisposable' interface is created.

2) Make classes 'IDisposable' if they create a thread or they add an object to a static or long lived collection. Remember a C# 'event' is a collection.

Here is a short article on Tips to Prevent Memory Leaks.

Answer 2

That doesn't really cause leaks, it just makes more work for the GC:

// slows GC
Label label = new Label();  
this.Controls.Add(label);  
this.Controls.Remove(label);  

// better  
Label label = new Label();  
this.Controls.Add(label);  
this.Controls.Remove(label);  
label.Dispose();

// best
using( Label label = new Label() )
{ 
    this.Controls.Add(label);  
    this.Controls.Remove(label);  
}

Leaving disposable components lying around like this is never much of a problem in a managed environment like .Net - that's a big part of what managed means.

You'll slow you app down, certainly. But you won't leave a mess for anything else.