views:

2612

answers:

6

Hello

I have created a thread that has a method that's running. But sometimes I will want to kill the thread even if the method is still working. How can I do this? I tried Thread.Abort() but it seems to show up a messagebox saying "Thread aborted". How should I go about this?

+4  A: 

You should really only call Abort() as a last resort. You can use a variable to sync this thread instead:

volatile bool shutdown = false;

void RunThread()
{
   while (!shutdown)
   {
      ...
   }
}

void StopThread()
{
   shutdown = true;
}

This allows your thread to cleanly finish what it was doing, leaving your app in a known good state.

Jon B
A: 

Aborting a thread is a very bad idea, since you cannot determine what the thread was doing at the time of the abort.

Instead, have a property that the thread can check, and that your external code can set. Let the thread check this boolean property when it's at a safe place to exit.

John Saunders
+15  A: 

Do not call Thread.Abort()!

Thread.Abort is dangerous. Instead you should cooperate with the thread so that it can be peacefully shut down. The thread needs to be designed so that it can be told to kill itself, for instance by having a boolean keepGoing flag that you set to false when you want the thread to stop. The thread would then have something like

while (keepGoing)
{
    /* Do work. */
}

If the thread may block in a Sleep or Wait then you can break it out of those functions by calling Thread.Interrupt(). The thread should then be prepared to handle a ThreadInterruptedException:

try
{
    while (keepGoing)
    {
        /* Do work. */
    }
}
catch (ThreadInterruptedException exception)
{
    /* Clean up. */
}
John Kugelman
Using exception handling to control program flow is a horrible idea. Use a WaitHandle instead.
Mark Seemann
I don't think it's that horrible. If your loop is not tight enough and it might take 30 seconds of processing before it finally knows that it should exit, an exception is the perfect way to stop it.
Jimbo
Mark, what if your thread is blocking for input and you need to make it stop somehow? It can block indefinitely, so Interrupting it and handling the exception is about the only way you can make it exit.
Lirik
+3  A: 

The most correct and thread-safe way is to use a WaitHandle to signal to the thread when it's supposed to stop. I mostly use ManualResetEvent.

In your thread, you can have:

private void RunThread()
{
    while(!this.flag.WaitOne(TimeSpan.FromMilliseconds(100)))
    {
        // ...
    }
}

where this.flag is an instance of ManualResetEvent. This means that you can call this.flag.Set() from outside the thread to stop the loop.

The WaitOne method will only return true when the flag is set. Otherwise, it will time out after the specified timeout (100 ms in the example) and the thread will run through the loop once more.

Mark Seemann
A: 

Aborting the thread is a great idea. Especially if the thread is performing very volatile, high-risk transactions on the core operating system, where leaving an atomic transaction in an unstable state could be detrimental to the host server.

Stu Pidasso
A: 

It is not a good idea to kill a thread. It is better to signal that it should stop and let it end gracefully. There are various different ways of doing this.

  • Use Thread.Interrupt to poke it if it is blocked.
  • Poll a flag variable.
  • Use the WaitHandle class to send a signal.

There is no need for me to rehash how each method can be used since I have already done so in this answer.

Brian Gideon