LabVIEW Idea Exchange

About LabVIEW Idea Exchange

Have a LabVIEW Idea?

  1. Browse by label or search in the LabVIEW Idea Exchange to see if your idea has previously been submitted. If your idea exists be sure to vote for the idea by giving it kudos to indicate your approval!
  2. If your idea has not been submitted click Post New Idea to submit a product idea to the LabVIEW Idea Exchange. Be sure to submit a separate post for each idea.
  3. Watch as the community gives your idea kudos and adds their input.
  4. As NI R&D considers the idea, they will change the idea status.
  5. Give kudos to other ideas that you would like to see in a future version of LabVIEW!
Showing results for 
Search instead for 
Did you mean: 

Abort All VIs in Project

Status: New

When improperly stopping a project that has launched asynchronous vis set to fire and forget, you end up with classes and libraries that are locked.


Reserved VIs.PNG 


There seems to be no way of unlocking them other than to close the project. There is an idea to abort called VIs when the parent stops but from the lack of kudos and by reading the comments it doesn't seem like a good one.


I know about and use the but it does not work in this case. The dropdown is empty:


Not running.PNG


Not even the LabVIEW Task Manager can help.



Task Manager.png


My idea is to have a button that does whatever closing the project does when it unlocks the class or library. Maybe this means it transparently closes the project and opens it again in the state it was in when the button was pressed. I don't know.


Abort Project.png



I know there are some similar ideas but as far as I can tell this is not a duplicate.

LabVIEW 2012


I like part of the way XControls handle this. They have a context menu item in the project for "Unlock Library for Editing". This is necessary because XControls are locked when any usage is in memory, not just when a VI is running. However, the functionality falls short. If a VI is running, this menu item opens a dialog showing the running VIs with no ability to do anything but close the dialog. I can't actually handle the situation. I am only informed of it.


This dialog should allow the user to abort all the needed VIs. Similar functionality should be available for any library or VI. If I'm looking at a reserved subVI and try to switch to edit mode, I should be given the option to abort the top level VIs so that I can edit.


Aborting is dangerous and you have to realize its affects before you do it. But we both know you're going to do it anyway, so why not make it easier.

Active Participant

It's been 8 years. How is this not a thing yet? Countless times I run into this when debugging large applications. Even a simple "show me what's running" button would go a long way. Then I can pop open the offender and kill it so I can move on with debugging without having to close and re-open the project.

Active Participant

Throwing another kudo and comment on this. An additional use case is in the Actor framework... it's pretty easy to accidentally create a deadlock (like launching an actor in Pre-launch Init). It's a pain in the butt to try to figure out which specific VI is blocking, especially if you are 4-5 levels of inheritance deep. You have to close the project to abort all of the currently running VI's, and most of the traditional tricks don't work because many of these running VI's are clones.