LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Labview executable does not exit memory when closed

Hello everyone. I have been tasked with upgrading some of our vis from labview 6.0 to 8.5.1 . I was able to create new executables and run the vis just fine in 8.5. However, when I close the vis in question, the window dissapears just fine, but the process remains in memory causing me to have to go to the task manager and manually kill the process. Does anyone know what generally might cause this sort of problem to occur? This did not happen when the program was in version 6.0. Thank you for your help.
0 Kudos
Message 1 of 21
(6,833 Views)
I asume that your VI does not call "Quit LabVIEW".
But without seeing the code, we cannot give you any further valuable hints.,....

Norbert
Norbert
----------------------------------------------------------------------------------------------------
CEO: What exactly is stopping us from doing this?
Expert: Geometry
Marketing Manager: Just ignore it.
0 Kudos
Message 2 of 21
(6,822 Views)

Hi pacman326,

do you use dynamically loaded vi´s? Maybe some of them are still in memory if you close your program.

Mike

0 Kudos
Message 3 of 21
(6,821 Views)
I went ahead and added an event handler "application instance close" and I added the quit labview module connected to a boolean constant of true. It's weird because the .vi running closes, but the executable remains in my task bar.

In other words, when I execute my .exe, I have ________.exe and _______.vi running. When I hit the red 'x' for my .vi, it closes but not the .exe. When I call file>quit in the .vi, they both close.

Edit: To be clearer, adding the above did not close the .exe portion when I hit the x out button in my .vi window.


Message Edited by pacman326 on 07-24-2008 10:03 AM
0 Kudos
Message 4 of 21
(6,814 Views)
To spark more interest, I converted another seperate vi and it does not create a .exe window like this vi does. I am going to try to go find the person who wrote this.
0 Kudos
Message 5 of 21
(6,798 Views)
Is there a "system exec.vi" in the VI?

Norbert
Norbert
----------------------------------------------------------------------------------------------------
CEO: What exactly is stopping us from doing this?
Expert: Geometry
Marketing Manager: Just ignore it.
0 Kudos
Message 6 of 21
(6,796 Views)
Didn't see that .vi in my dependency list.
0 Kudos
Message 7 of 21
(6,790 Views)

Pacman, did you ever figure out what was causing this?  I'm experiencing exactly the same situation, and cannot get the executable instance out of the Windows process list without explicitly stopping the process.

 

I am using "Quit Labview"; interestingly, if I comment that out of my code, I get an executable that just stops and I have to hit the upper-right-corner "x" to close the window - in this case, there is NO leftover instance in the Windows task manager.  But for some reason, the "Quit Labview" vi can't seem to be able to finish the job.

 

- Brian

 

0 Kudos
Message 8 of 21
(6,595 Views)
Hi, I have seen the same problem in my project, How did you solve this problem, I cannot end the labview.exe even from the task mamager manually. thanks in advance,
0 Kudos
Message 9 of 21
(6,154 Views)

thedoctor,

 

Did you try following the steps in this post? It suggestes few options to close the .exe programatically.

Tarek B
Applications Engineer
National Instruments
0 Kudos
Message 10 of 21
(6,122 Views)