10-01-2009 04:31 PM
Hi,
I am trying to resolve an intermittent issue where the LabVIEW executable closes, but stays in the "list of processes" in Task Manager.
LabVIEW exe does have the code to exit LabVIEW. It works as expected at times. However, at times when the Executable is closed, it will disappear from "Applications", but will stay put in "Processes" in Task Manager. During such instances, when the executable is opened, two executables show up in "Processes". I am concerned when this happens and was wondering if there is a way to clean it up or kill the process from Task Manager. Inputs/suggestions are welcome. Thank you.
10-01-2009 05:25 PM
Is this the LabVIEW development enviornment, or a particular LabVIEW EXE that you compiled from a project?
Maybe an application reference in your code that is not closed properly? Although... it should whether you explicitly close it or not.
10-01-2009 07:11 PM
10-02-2009 12:57 AM
Out of interest what method do you use to close the application and references?
What does the program do? What processes does it use? What operating system? Which version of LV?
10-02-2009 12:46 PM
Sounds to me like the Run-Time is sticking around in memory after the specific application is closed. Sorry, I don't have a solution. Can you make a very simple VI, compile and install it on your target machine to try and determine if the problem is with your application or with the LabVIEW run-time?
My knee-jerk reaction would be to uninstall the run-time, reboot, and re-install the run-time.
-Nic