LV 2012 compatibility bugs with Windows XP

[MinerHokieRamp]

---

@Kyle97330 wrote:

Do you ever call any of your subVIs using the "Start Asynchronous Call" function?

I've had issues stopping LV when running those VIs and they don't stop properly.

---

I've never used "Start Asynchronous Call". I wasn't familiar with it so I looked for it on ni.com.

Thanks,

[MinerHokieRamp]

---

@Kyle97330 wrote:

Do you ever call any of your subVIs using the "Start Asynchronous Call" function?

I've had issues stopping LV when running those VIs and they don't stop properly.

---

Perhaps an executable will eliminate this annoying problem.

Thanks,

[aflojo · Accepted solution]

It sounds like a reference to a top level VI is getting left open and therefore, LabVIEW is getting hung. I found an example VI that you can run to find all your VIs that are open.

https://forums.ni.com/t5/Example-Code/Finding-Running-VIs/ta-p/3996230

I would suggest running it the next time LabVIEW application tab gets stuck in the windows task bar and make sure that all your VI references are getting closed.

[MinerHokieRamp]

aflojo wrote:

It sounds like a reference to a top level VI is getting left open and therefore, LabVIEW is getting hung. I found an example VI that you can run to find all your VIs that are open.

https://forums.ni.com/t5/Example-Code/Finding-Running-VIs/ta-p/3996230

I would suggest running it the next time LabVIEW application tab gets stuck in the windows task bar and make sure that all your VI references are getting closed.

---

---

---

After reading your suggestion, I noticed that LV only hangs up when one subVI has been called.

The FP.STATE property of that VI was alternately set to "Standard" and "Hidden" from a main VI button toggle. 

So, I changed the FP.CLOSE setting from "Hidden" to "Closed" and LV didn't hang up during initial tests. Looks promising; I'll try it for a few days and provide an update.

Thanks,

Jeff