To Dispose() or Not To Dispose() elements in an array of IDisposable objects?

Denis Published at Dev

Denis

There are lots of examples of Arrays or Lists of IDisposable objects being returned from functions in .NET. For example, Process.GetProcesses().

If I call that method is it my responsibility to Dispose() of all the members of the array as I iterate through them?
Why should it be my responsibility since I never created the objects and the array that I was given is just pointers to the objects which were created outside of my code.

I always thought it was the creator's burden to Dispose(). So what is the proper rule here?

Servy

There is no general rule. It's going to depend on the situation, and how the method in question is designed, as to whether or not "you" are responsible for disposing of objects you have access to. This is where documentation is often important to help users of the type understand their responsibilities.

I always thought it was the creator's burden to Dispose()

This cannot be strictly true. It is sometimes the case that a disposable object will out-live the lifetime of the block of code creating it. While it simplest when the creator can dispose of the object, sometimes it's simply impossible for them to be able to. When returning a disposable object from a method is one situation where it's often not be possible for the code creating the disposable object to clean it up, as it's lifetime needs to be smaller than the lifetime of the disposable object.

Collected from the Internet

Please contact [email protected] to delete if infringement.

edited at2021-02-18

Comments

0 comments

From Dev

Related Related

Article

To Dispose() or Not To Dispose() elements in an array of IDisposable objects?

To Dispose() or Not To Dispose() elements in an array of IDisposable objects?

Does NUnit dispose of objects that implement IDisposable?

Dispose will dispose objects that are still referenced?

Why is IDisposable instantly calling Dispose()?

Dispose of objects in user control?

How to Dispose SharpDX objects

Font objects dispose in InitializeComponent

Would MVC call Dispose if your ViewModel was IDisposable?

Does disposing an object dispose of all IDisposable properties?

When/how is IDisposable.Dispose called?

Why code analyzers recommend to dispose IDisposable fields?

Where to call Dispose() of IDisposable created in constructor?

Reasoning behind implementing Dispose but not implement IDisposable?

Would MVC call Dispose if your ViewModel was IDisposable?

C++ dispose array

How to properly dispose objects in Flambe?

Must implement Sub Dispose() for interface 'System.IDisposable'

IDisposable.Dispose is never called after exception in using block

Do i need to Dispose Stream when i Pass it to IDisposable class?

If I have a Dispose method, must I implement IDisposable?

Using Unity, how do you automatically dispose an IDisposable?

What should I do when inheriting IDisposable with nothing to dispose?

How does WebResponse not have "Dispose" publically visible when it implements IDisposable?

C# calling IDisposable.Dispose() vs making object null

How can i dispose IDisposable when it is declared in a parameter?

IDisposable.Dispose() not called in Release mode for async method

Using Unity, how do you automatically dispose an IDisposable?

Must implement Sub Dispose() for interface 'System.IDisposable'

IDisposable.Dispose is never called after exception in using block

Warning: Do not dispose objects multiple times