How can I find which VIs are actively running?

[RavensFan]

Perhaps this kind of information can only be accurately determined if the VI's are running slow such as in highlight execution.  The question would be equivalent to which VI or subVI currenlty has the slow moving execution dot moving along its wire?

[FermWorks]

No matter how slow, it can't be accurate because there's always a chance of querying the state right before a transition, but yes, there would be less of a chance.

In my case, I want to find which VI among thousands is stuck running, that's blocking execution of other things.

[robdye]

There has been this idea floating around for a while, maybe it has even made it to the LV Idea Exchange, that the hierarchy window could have a mode that displays an approximation of the current execution state of your VIs. Of course, the state of the program could change drastically just during the time it takes to draw this state, so it may be difficult to do this in a comprehensible way. Unless there was a way to stop all threads and get an atomic snapshot of the program state, it could easily draw a depiction that was, in fact, impossible. For instance, two subVIs being depicted as called simultaneously when in actuality they are only called sequentially.

OK. I did a quick search for "execution hierarchy" in the LabVIEW Idea Exchange and this is a popular topic. Remember: your votes actually count in the Idea Exchange!

[FermWorks]

Could be useful..... but not for a hierarchy of hundreds or thousands. : (

[JÞB]

---

@MegKB wrote:

No matter how slow, it can't be accurate because there's always a chance of querying the state right before a transition, but yes, there would be less of a chance.

In my case, I want to find which VI among thousands is stuck running, that's blocking execution of other things.

---

Oh, That's a simpler matter.  Just don't write bugs and the point becomes moot.

Spoiler

No wonder why I never needed this before

[paul_cardinale]

This is the only thing left I can think of:  For each VI you want to check, make sure its FP is open and in front.  Then ask Windows to hand you an image of the run button (See attachment).

[paul_cardinale]

Try this kludge.

[FermWorks]

Wow, impressive, visual inspection! I thought of this possibility but you actually implemented it, cool!

Unfortunately, I have literally thousands of VIs.  : (  Hope your solution helps somebody out there.

I'm going to move on to other ideas for troubleshooting my problem instead of trying to find out what's currently running.

Thanks, everybody.

[JÞB]

---

@MegKB wrote:

Wow, impressive, visual inspection! I thought of this possibility but you actually implemented it, cool!

Unfortunately, I have literally thousands of VIs.  : (  Hope your solution helps somebody out there.

I'm going to move on to other ideas for troubleshooting my problem instead of trying to find out what's currently running.

Thanks, everybody.

---

Do consider the suggestion to "just not write bugs..."

Debugging does get easier when there are no bugs in the first place

[andrew_johnson]

Reallly? Your only contribution is to insinuate that someone "just not write bugs?"

I'm surprised you were given an Alliance membership with an attitude like that.