Invoking of Dispose method in instance of a Task

Question

0.00/5 (No votes)

See more:

Hi guys.
I come here with one question related to Dispose method in Task class.
How mandatory this method is ? And do i need to invoke it every time when i finished to work with task instance.
I have investigated Dispose method with help of Reflector, and i found that internally when we calling it it perform some clean up stuff especially against ManualResetEvent.

C#

protected virtual void Dispose(bool disposing)
{
    if (disposing)
    {
        if ((this.Options & 0x4000) != TaskCreationOptions.None)
        {
            return;
        }
        if (!this.IsCompleted)
        {
            throw new InvalidOperationException(Environment.GetResourceString("Task_Dispose_NotCompleted"));
        }
        ContingentProperties contingentProperties = this.m_contingentProperties;
        if (contingentProperties != null)
        {
            ManualResetEventSlim completionEvent = contingentProperties.m_completionEvent;
            if (completionEvent != null)
            {
                contingentProperties.m_completionEvent = null;
                if (!completionEvent.IsSet)
                {
                    completionEvent.Set();
                }
                completionEvent.Dispose();
            }
        }
    }
    this.m_stateFlags |= 0x40000;
}

The main concern about that lies in next:
Quite often i use such construction:

C#

Task.Factory.StartNew(()=>{ .. some stufff });

How important in such case to invoke Dispose ???

Posted 17-Dec-12 4:19am

Oleksandr Kulchytskyi

Updated 24-Dec-12 1:32am

v3

Add a Solution

1 solution

Add a Solution

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

OriginalGriff · Answer 1 · 2012-12-24T01:44:00

It depends.

Which may not be much help, but...

You should call Dispose on any object which explicitly implements it, because the idea is that the object contains or uses resources which are in scarce supply, or which use a lot of "space" - be that memory or something else. If Dispose isn't called (either explicitly, or by enclosing it in a using block) then the resources are not released until the Garbage Collector is called in and decides that the object is no longer needed - at which point it will call Dispose on the object. Because this only happens in normal circumstances when memory starts to run low, it man not happen for several hours, or days, or weeks - or until the application terminates.

If your objects don't implement IDisposable then you shouldn't need to explicitly call Dispose.

Some of the objects (and by no means all) which you should Dispose are SqlCommand, SqlConnection, all Graphics objects, Fonts, Brushes, Bitmaps and so forth.

Invoking of Dispose method in instance of a Task

1 solution

Solution 1

Add your solution here

Preview 0

Invoking of Dispose method in instance of a Task

1 solution

Solution 1

Add your solution here

Preview 0

Existing Members

...or Join us