Exit delay

Question

I use the Exit function to terminate execution of a labview built exe.  While the front panel disappears immediately, the exe remains in memory for 50 seconds before finally terminating. If I run the source it can take as long as 90 seconds before Labview finally terminates. 
This is more than a petty annoyance.  If a user runs the program, terminates it and then wants to start it again, she can't and there is no obvious reason why not.
Furthermore if I start Labview without any vi indicated and select Exit from the labview Getting Started screen it can take close to a minute to go away.
Note:  I am running Labview 2011 for Windows 7 on a recent Macbook Pro using VMware fusion. Could all these layers of software be the cause?  Does anything like this happen on real Windows machines?
Solved!
Go to Solution.

Answer 1

While this isn't wanted behavior, sometimes it is unavoidable.  It takes time to release all the resources.  Firefox is like that for me.  Admittedly, I probably have way too many extensions loaded, but sometimes it takes over 30 seconds to unload, even though it is gone from the screen.  When you try and run it again, it says it's still running.
Bill
(Mid-Level minion.)
My support system ensures that I don't look totally incompetent.
Proud to say that I've progressed beyond knowing just enough to be dangerous. I now know enough to know that I have no clue about anything at all.