Process continues to run after Application.Exit()

Hot Topic

(Newbie) Listbox.SelectedIndex problem
How can I manage MessageBox result ?
wildcard problem
Help i'm trying to query from sql with tableadapter
why setlocale(LC_ALL,"Russian") for console application doesn't work in visual studio .net 2003? But it works in VS 2005...
urgent !!!!listbox inserting problem
More text box Stuff?
Modify a structure from ArrayList
Simple Pause
Java Language Conversion Assistant 3.0

VS Express Editions

PSDK install fails
Blue Rectangle in Breakpoint Margin
Is vc++ 6.0 good
Timer
how do you find the friendly name of an application???
How to use CrystalReports with Visual Basic Express Edition
Deploying .MSI file
SQL Server 2005 Express Samples (Adventure Works) with Visual Web Developer
Numeric Problem
Missing C++ Templates

Process continues to run after Application.Exit()

When the user clicks on my Exit menu command I call Close() followed by Application.Exit(). The GUI goes away as expected but the process is still listed in Task Manager. What do I need to do to really terminate the process




Answer this question

Process continues to run after Application.Exit()

  • nathandyck

    You might leave unmanaged resources allocated if you use Environment.Exit()

    I see now that Application.Exit() should inform all messageloops to terminate. I did not see that when I made a test application for multi-threading. Maybe it was because I was only debugging it.



  • m_r

    Do you have multiple calls to Application.Run() or other threads running

    You might need to abort running threads and call Application.Exit() for every Applicat ion.Run()



  • Pr0fess0rX

    Do you have any non background threads running

    When creating a thread that you don’t want to manually have to clean up when the app exits, it is a good idea to set it’s IsBackground property to true so that it will die along with the parent.



  • SPAWN_UK

    Well, I did not explicitly start any additional threads, but it's obvious that the WebBrowser control uses background threads to get its work done. So, I don't really know what other threads might be running. And VS 2005 C# *Express* does not seem to have a facility for displaying the threads that belong to the process being debugged.



  • Andy Eastwell

    Another suggestion given to me was Environment.Exit() with the caveat that is more brute force, less graceful. Any problems I should be aware of with that approach

  • Process continues to run after Application.Exit()
Answer this question