Home/ Questions/Q 80769
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-10T21:21:17+00:00

In my app I’ve got a thread which displays for some time please wait

  • 0

In my app I’ve got a thread which displays for some time ‘please wait’ dialog window, sometimes it is a very tiny amout of time and there is some glitch while drawing UI (I guess).

I get the exception ‘Thread was being aborted’ and completly have no idea how get rid of it. I mean Catch that exception in some way, or in some other way hide it from user. This exception has got nothing to do with rest of my app and that error in any way doesn’t affect it. Appears randomly and it is hard to recreate on a call.

I tried in various ways to catch that exception by side of code which starts and stops thread with dialog window but it seems that error apparently is by side some other thread which dispalys window in my newly created thread.

Here is a code sample, part of static class with useful stuff, of course I don’t say that is good way to solve this kind of ‘busy’ situation but I want to solve this problem. Thread.Sleep(500); or other try/catch improvments doesn’t help me to avoid that thread exception.

    public static bool alreadyBusy = false;     public static BusyIndicator bi = new BusyIndicator('');     public static Thread backgroundOpertionThread;      public static void showBusy(bool isBusy, System.Windows.Forms.Form hostform, string message)     {         Common.busyMessage = message;         if (isBusy)         {             Common.alreadyBusy = true;             backgroundOpertionThread = new Thread(new ThreadStart(showBusy));             Thread.Sleep(500);             if (hostform != null)             {                 hostform.Enabled = false;                 hostform.SuspendLayout();             }             backgroundOpertionThread.Start();          }         else         {              backgroundOpertionThread.Abort();             Thread.Sleep(500);             Common.alreadyBusy = false;             if (hostform != null)             {                 hostform.Enabled = true;                 hostform.ResumeLayout();             }         }     }      public static void showBusy()     {         BusyIndicator bir = new BusyIndicator(Common.busyMessage);         bir.ShowDialog();     }

Any ideas?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Do not use Thread.Abort. This method is reserved for when the .NET runtime needs to forcibly kill threads in order to unload your program.

    You can only ‘safely’ use this if you’re about to unload an AppDomain and want to get rid of threads running in it first.

    To get rid of a thread, write it in cooperative mode. This means that the thread should periodically check some kind of flag, and if the flag is set, exit normally out of the thread method. To ‘kill’ the thread, simply set the flag and wait for the thread to exit.

    You can use an Event-object or a simple boolean variable for this flag.

    But do not use Thread.Abort.

    • 0