Why LabVIEW can be only closed via task manager (still)?

[Norbert_B]

What you can do is to check if Windows Event Log shows up weird things. Maybe you can find out the source (DLL, EXE, ...?) of the zombie behavior.

Norbert

[Blokk]

What is funny, that I did not have this behaviour since I started this thread...I guess the bug got scared of you people??? 😄

As a workaround (speed up the kill task procedure), I installed again the handy tool from Hooovahh :

https://lavag.org/topic/11333-labview-tray-launcher/?do=findComment&comment=116021

[Hooovahh]

Hey that's me.  Yeah I've been meaning to update that, I think there is a bug with sometimes not opening a VI in the selected instance.

Anyway to be on topic a bit.  The only time I saw something like this, is when I was using a toolkit that was opening VI references and not closing them.  If you waited a realllly long time LabVIEW would close itself on exit but it took forever.  This also manifested itself in built EXEs.  It took quite a bit of testing to isolate it and reproduce it to find the place where a close reference was needed.

I don't think this is your situation because you claim it happens on simple VIs from the forums.  I'd just try to come up with a set of steps that can reliably reproduce the issue, and then try to isolate what is causing it.  But I would suspect is is some kind of plugin that is loaded, and not the unclosed references that my issue was.

[Blokk]

Hmm, I will try to reproduce the bug when I use the LAVA Code Capture Toolkit...It might cause the bug...?

[Blokk]

No, at least not after one try: I have created a snippet, but I was able to exit LV properly after that...

[terickson]

I have seen this and it is usually due to a reference not getting closed or a front panel window that was hidden but the VI not closed.  To help troubleshoot, right click on the LabVIEW icon on the task bar.  That should show a list of recently opened VI's.  Choose any one of them.  After that VI opens, choose View->VI Hierarchy from the LabVIEW Menu.  It will show the VI that you opened as well as any other VI in memory.  This may help you track down the issue.