Exit delay

[David_Lieberman]

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?

[smercurio_fc]

Sounds like you have some references to external components or libraries that are taking a long time to close down. Without you telling us what you actually have in your code all we can do is play guessing games.

[billko]

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.

[David_Lieberman]

OK.  here is an executable I created to demonstrate the problem.  From the time I selected exit from the file menu it took 50 seconds for the program to exit memory.

[David_Lieberman]

Sorry, I sent the vi not an executable but the issue is the same.

[smercurio_fc]

I tried your VI on a Windox XP virtual machine with LabVIEW 2011. The virtual machine was running inside a Windows 7 computer. The VI exited (and consequently LabVIEW as well) within a couple of seconds. So, there must be something going on that's specific to your setup. Do you see this only when using the Exit function?

[David_Lieberman · Accepted solution]

OK.  I dredged up a real Windows machine and tried the executable.  It terminated in 2 seconds.  So obviously it has something to do with my VMware virtual machine setup.  Thanks for your help.