dispose

I've been reading a lot about this since I've been asked to fix a C# application that has memory leaking problems, but I haven't found an answer for these 2 issues: Consider the following code: private static ArrayList list = new ArrayList(); public void Function() { list.add(object1); list.add(object2); //didn't call clear() prior to reusing list list = new ArrayList(); } Since the list wasn't cleared before creating a new one, will this generate some sort of garbage that won't be released after the static list itself is disposed? The second issue is regarding Form.Dispose(). I see that a lot

I have been pondering why it is recommended that we should not release managed resources inside finalize. If you see the code example at http://msdn.microsoft.com/en-us/library/system.gc.suppressfinalize.aspx , and search for string "Dispose(bool disposing) executes in two distinct scenarios" and read that comment, you will understand what I mean. Only possibility I can think of is that it probably has something to do with the fact that it is not possible to predict when finalizer will get called. Does anyone know the right answer ? thanks, mishal Jon Skeet If you're referencing another object

I've apparently worked myself into a bad coding habit. Here is an example of the code I've been writing: using(StreamReader sr = new StreamReader(File.Open("somefile.txt", FileMode.Open))) { //read file } File.Move("somefile.txt", "somefile.bak"); //can't move, get exception that I the file is open I thought that because the using clause explicitly called Close() and Dispose() on the StreamReader that the FileStream would be closed as well. The only way I could fix the problem I was having was by changing the above block to this: using(FileStream fs = File.Open("somefile.txt", FileMode.Open))

I have some user controls in a windows form. I wonder if i set the Font property of the main form, will its child get a) a copy of the new Font , or b) a reference to the new Font , or c) nothing? Does a font need to be disposed? For example, can I do the following code safely? form.Font = new Font(...); Will a font get disposed automatically when the parent ( Form or UserControl ) is disposed? Thanks, Gilbert Both. The Font property is its own .NET object. Winforms however caches the native Windows font, they are fairly expensive to create. The .NET wrapper object is quite small. Yes. The

As MemoryStream is an unmanaged resource does it always have to be disposed? Given: 1) A method is invoked. 2) A MemoryStream object is created (MemoryStream ms = new MemoryStream();). 3) An exception occurs and is caught from the invoking classes. The reference on the MemoryStream object is therefore lost. Does this scenario need a try/finally-block (or using-statement)? In general, all disposable objects must always be disposed. However, MemoryStream doesn't actually need to be disposed, since it doesn't have any unmanaged resources. (It's just a byte[] and an int ) The only reason it's

Do I need to call dispose in the finally block for SqlTransaction? Pretend the developer didnt use USING anywhere, and just try/catch. SqlTransaction sqlTrans = con.BeginTransaction(); try { //Do Work sqlTrans.Commit() } catch (Exception ex) { sqlTrans.Rollback(); } finally { sqlTrans.Dispose(); con.Dispose(); } Tim Schmelter Do I need to use try-finally or the using -statement to dispose the SqlTransaction ? It does not hurt to have it. This is true for every class implementing IDisposable , otherwise it would not implement this interface. But normally the garbage collector would deal with it

When can i cleanup objects stored in static variables in C#? I have a static variable that is lazily initialized : public class Sqm { private static Lazy<Sqm> _default = new Lazy<Sqm>(); public static Sqm Default { get { return _default.Value; } } } Note : That i've just changed Foo to be a static class. It doesn't change the question in any way if Foo is static or not. But some people are convinced that there is no way that an instance of Sqm could be constructed without first constructing an instance of Foo . Even if i did create a Foo object; even if i created 100 of them, it wouldn't help