threadabortexception

UPDATE: I don't think this question is a duplicate of Can ThreadAbortException skip finally? because (1) I'm not creating another thread, so there's no possibility of a race condition, and (2) this behavior only occurs if the finally block contains an await , which that other question doesn't mention. Consider this console program: class Program { static void Main() { try { T().GetAwaiter().GetResult(); } catch (ThreadAbortException) { Thread.ResetAbort(); } catch { } } static async Task Abort() { //await Task.Delay(1); // A Thread.CurrentThread.Abort(); // B } static async Task T() { try {

I was playing around with Constrained Execution Regions tonight to better round out my understanding of the finer details. I have used them on occasion before, but in those cases I mostly adhered strictly to established patterns. Anyway, I noticed something peculiar that I cannot quite explain. Consider the following code. Note, I targeted .NET 4.5 and I tested it with a Release build without the debugger attached. public class Program { public static void Main(string[] args) { bool toggle = false; bool didfinally = false; var thread = new Thread( () => { Console.WriteLine("running");

Please do not set duplicate flag on this qustion - it is not about "why ThreadAbortException occurs", it is about "why w3wp.exe process terminates after ThreadAbortException". Let's say we have simple web application with following code sample: protected void Page_Load(object sender, EventArgs e) { Response.Redirect("http://google.com"); } Which by fact means something like (see Is Response.End() considered harmful? ): protected void Page_Load(object sender, EventArgs e) { ...response write some data... System.Threading.Thread.CurrentThread.Abort(); } On my machine (Windows 10 Pro + IIS) this

I am calling ChannelServer.ListeningThread.Abort on the following thread, however nothing seems to happen. I would like to be more specific, but I can't think of anything more. There seems to be no ThreadAbortException that is thrown, and this exception should be thrown regardless of the blocking listener (it works perfectly on threads that are blockingly-receiving). Important EDIT : With a ManualResetEvent.WaitOne instead of AcceptSocket , as Lyrik has suggested for testing, it works perfectly. How come AcceptSocket blocks the ThreadAbortException ? LINK : This forum thread seems to discuss