What’s wrong with using Thread.Abort()

by

In addition to all of the other good answers here, let me add that there is no guarantee whatsoever that a call to Thread.Abort will actually abort the thread in question, ever. It is possible (though not particularly easy) to “harden” a thread against being aborted. If, for example, you are aborting a thread because you believe it to be running hostile code then the hostile code could be resisting its own destruction.

If you have a long-running operation involving code that you do not own that must be taken down cleanly, the correct way to do this is to put that code in its own process, not its own thread. (And preferably in a highly security-restricted appdomain in that process.) You can then cleanly kill the process.

In short, Thread.Abort is at best indicative of bad design, possibly unreliable, and extremely dangerous. It should be avoided at all costs; the only time you should ever even consider aborting a thread is in some sort of “emergency shutdown” code where you are attempting to tear down an appdomain as cleanly as possible.

More Related Contents:

  1. Creating a blocking Queue in .NET?
  2. What’s the difference between Invoke() and BeginInvoke()
  3. If async-await doesn’t create any additional threads, then how does it make applications responsive?
  4. Task vs Thread differences [duplicate]
  5. Question about terminating a thread cleanly in .NET
  6. How do I update the GUI from another thread?
  7. What operations are atomic in C#?
  8. Accessing UI (Main) Thread safely in WPF
  9. Multi-threaded splash screen in C#?
  10. ‘using’ statement vs ‘try finally’
  11. Thread.Sleep for less than 1 millisecond
  12. Returning a value from thread?
  13. Async process start and wait for it to finish
  14. Is it OK to use a string as a lock object?
  15. STAThread and multithreading
  16. Monitor vs lock
  17. Proper way to Dispose of a BackGroundWorker
  18. EF Data Context – Async/Await & Multithreading
  19. Why am I getting this error:”Cross-thread operation not valid: Control lbFolders accessed from a thread other than the thread it was created on.”?
  20. Thread safe collections in .NET
  21. Properly locking a List in MultiThreaded Scenarios?
  22. Can you link to a good example of using BackgroundWorker without placing it on a form as a component?
  23. When is ReaderWriterLockSlim better than a simple lock?
  24. Create multiple threads and wait for all of them to complete
  25. How to correctly read an Interlocked.Increment’ed int field?
  26. ConcurrentDictionary Pitfall – Are delegates factories from GetOrAdd and AddOrUpdate synchronized?
  27. Should thread-safe class have a memory barrier at the end of its constructor?
  28. ReaderWriterLock vs lock{}
  29. Async and Await with For Loop [duplicate]
  30. When exactly does .NET Monitor go to kernel-mode?

Leave a Comment