Closing a locked up VI without using task Manager to kill the Labview development environment

[RTSLVU]

Honestly this has always bugged me. Occasionally with developing a program I will have errors that cause the VI to lockup. The only way I know of to close them is to use Windows Task Manager to kill LabVIEW. This can cause loss of unsaved changes in my project. Sure I try to save everything before I run a VI for the first time, but sometimes I forget.

There has to be a better way to abort a locked up VI?

[GerdW]

Hi RTSLVU,

---

@RTSLVU wrote:

Occasionally with developing a program I will have errors that cause the VI to lockup. The only way I know of to close them is to use Windows Task Manager to kill LabVIEW.

---

What happens when you close the project in this specific case?

(When you develop a program you will use LabVIEW projects, don't you!?)

[Bob_Schor]

I once wrote a little VI called "Abort Top-Level VIs" (I just looked -- the Version I have is LabVIEW 2011!).  If memory serves, we were trying to take videos from multiple (at least a dozen) Basler TCP/IP cameras simultaneously, and when testing the code, it would sometimes "lock up".

The code was fairly simple.  It ran the Application Property "All VIs, and if it wasn't itself, would check its Exec State and if set to "Run top level", would abort it.  We didn't use it often, and I haven't used it when (more modern) LabVIEW throws a snit and refuses to close (hello, Task Manager!), but so far, on re-opening, the Recovery Dialog usually saves my rear end.

Maybe LabVIEW 24 won't hang?

Bob Schor

[RTSLVU]

---

@GerdW wrote:

Hi RTSLVU,

---

@RTSLVU wrote:

Occasionally with developing a program I will have errors that cause the VI to lockup. The only way I know of to close them is to use Windows Task Manager to kill LabVIEW.

---

What happens when you close the project in this specific case?

(When you develop a program you will use LabVIEW projects, don't you!?)

---

Yes I do use LabVIEW projects...

Closing the project gives me a warning message about closing the project with running VI's, pressing the "close" button on that warning message closes the project but not the VI. Like it can't close a locked up VI when the running VI is locked up.

I guess the only thing I can to is remember to close the project before I kill it with Task Manager...

[jcarmody]

I submitted this to the LAVA code repository in 2009.  I still use it.

[Hooovahh]

I also have a LAVA thing.  I called it the LabVIEW Tray Launcher.  It has a bunch of features but one of them is an "abort all running VIs" which runs the abort all VI, in all versions of LabVIEW that are open.  I haven't updated it in years so it is possible something broke.  It also showed what versions of LabVIEW can open a VI you tried to open, allows you to run or restart LabVIEW from the system tray, and prevent a Run On Open behavior of VIs.

[RTSLVU]

I have to register before I can download from the LAVA site, but for some reason i am not allowed to register?

I do not have an existing user account on LAVA... 

[Hooovahh]

---

@RTSLVU wrote:

I have to register before I can download from the LAVA site, but for some reason i am not allowed to register?

---

That is a weird one.  I've contacted the site admin but it is possible your IP was banned for spam.  I don't know of any reason why it wouldn't all creating a user.  Attached is the Abort JCarmody linked to.  I can't attach my source because the attachment is too large.  But the full installer is linked in the release which is here.

[RTSLVU]

---

@Hooovahh wrote:

---

@RTSLVU wrote:

I have to register before I can download from the LAVA site, but for some reason i am not allowed to register?

---

That is a weird one.  I've contacted the site admin but it is possible your IP was banned for spam.  I don't know of any reason why it wouldn't all creating a user.  Attached is the Abort JCarmody linked to.  I can't attach my source because the attachment is too large.  But the full installer is linked in the release which is here.

---

Thanks...

My company uses "Forcepoint" and I am guessing that part of it is some kind of VPN, because my IP geolocates to a Forcepoint exit point in southern California but I am in Northwest Washington. Maybe that is confusing things?

[RTSLVU]

Hmmmm.... This is not working for me. 

It tries but then Abort.vi locks up.