Thread.Abort is a sure path to data corruption and crashes. The vast majority of code out here is not ready to handle async exceptions. It's fine to use Thread.Abort on an AppDomain you intend to unload right away, but that's pretty much it.
On Mon, Dec 16, 2013 at 9:40 PM, Edward Ned Harvey (mono) < [email protected]> wrote: > > From: [email protected] [mailto:mono-list- > > [email protected]] On Behalf Of mickeyf > > > > Thread.Abort is now considered a no-no. What is the best practice to > > correctly dispose of threads that have outlived their usefulness? > > For most purposes, I would say you should be using ThreadPool. Are you? > Or do you have a good reason not to? > _______________________________________________ > Mono-list maillist - [email protected] > http://lists.ximian.com/mailman/listinfo/mono-list >
_______________________________________________ Mono-list maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-list
