Winform is closed but it is still running in the program list via Task Manager

raja ramesh

15y12.8kAzure

Hi,
I have written a windows application and when I try to exit the program with the following code

private void KYRPlusRadForm_FormClosing(...)
{
var res1 = MessageBox.Show(this, "Are yor sure?", "Exit",
MessageBoxButtons.YesNo, MessageBoxIcon.Warning);
if (res1 == DialogResult.No)
{
e.Cancel = true;
}
else
{
this.Dispose();
}
}
private void KYRPlusRadForm_FormClosed(object sender,
FormClosedEventArgs e)
{
Application.Exit();
}
the form is closed, but it is still running in the program list via Task Manager.

How do you close and exit a program perminantly in C#?

3 Replies

Know the answer? Post it — somebody with the same question will find it here.

Sam Hobbs15y ago
Beginners have a tendency to call Dispose when they do not need to and therefore they sometimes get problems resulting from using Dispose. You should at least remove the call to Dispose. It seems probable to me that the Dispose does not close the window, but I am not sure except that I am sure you don't need the Dispose.

You should call Close() to exit the application. That will work if there is just one form. If there is another form then you probably can close that form at the same time. Closing all forms will cause the message loop to stop and then the program will stop. Calling Application.Exit() might not give the form(s) an opportunity to do whatever they need to do when they are closed normally.
Vulpes15y ago
When a Windows Form process is continuing after the application has apparently closed, it's generally a sign that there's a foreground thread (other than the main UI thread) still running - a process can't end until all its foreground threads have terminated.

This can occur if you create and start your own threads but forget to set their IsBackground property to true - it's false by default. If you start threads via the threadpool or a BackGroundWorker, then the threads are automatically background threads.

If you still can't figure it out, then Jaganathan's solution of calling Environment.Exit always works by killing the process and all its threads stone dead even if this can sometimes be a bit drastic for a GUI application.
Jaganathan Bantheswaran15y ago
Hi,

Use Environment.Exit(0) in Closed event.