Identification implementation for a class that contains streams

Question

Good morning! Suppose we have the following class:

class MultithreadOperation : IDisposable
{
    private IList<Thread> operationThreads;

    public void StartOperation()
    {
          // Initialize and start threads and put them to operationThreads
    }

    public void StopOperation()
    {
          // Aborts each thread.
    }

    public void Dispose()
    {
          Dispose(true);
          GC.SuppressFinalize(this);
    }

    protected virtual void Dispose(bool disposing)
    {
         if (!disposed)
         {
              disposed = true;
              if (disposing)
              {
                    // Release managed resources.
                    #1:
                    StopOperation();
              }
              // Release unmanaged resources.
              #2:
              StopOperation();
         }
    }

    ~MultithreadOperation()
    {
         Dispose(false);
    }
}

Actually, I need to stop all threads if the instance is deleted. In addition, I need to stop all threads if the instance is garbage collected (otherwise the threads will still be alive, which is bad for me). It is definitely, completely legal to refer to the StopOperation () method in place # 1.

I want to know if there are any pitfalls if we call StopOperation () in place # 2? As far as I understand, the list of threads may already be garbage collected when ~ MultithreadOperation () is executed. In addition, I saw many recommendations to avoid code that references managed resources in the Finalize implementation, especially instance fields.

. !

Answer 1

. , , , Dispose() - . , . , ​​ , , , .

, , , . CLR 2 , , .

Answer 2

StopOperation # 2, :

• List Thread .
• , StopOperation , , , .

, ( Thread.Abort) . , () . ( ), ( ) .

- :

• . , , .
• StopOperation , . , . , Thread.Join.
• StopOperation Dispose №1.

, , Dispose? . .

• . , . . , , . , Thread.Interrupt, , Thread.
• , . , , (.. ). , .