99 FAQ

It's important to differentiate between VI clones and DQMH Cloneable instances.

The View → Browse Relationships menu item shows aspects of the current VI and its hierarchy. Reentrant Items displays the Reentrant Original item and all clones of the reentrant VI.

For reentrant VIs that are set to Shared clone reentrant execution, “LabVIEW allocates a pool of clones, initially populated with one clone, to share amongst callers. When a caller calls a shared clone VI, it pulls a clone from the pool and returns the clone when the call finishes executing. If the pool is empty when a caller calls a shared clone VI, LabVIEW creates a new clone for that call and places the clone in the pool when execution finishes, thereby expanding the clone pool” (LabVIEW Online Help).

Seeing as DQMH uses Open VI Reference with option 0x40 (Enable simultaneous calls on reentrant VIs) for starting instances of Cloneable Modules, and LabVIEW therefore has no static way of telling how many cloneable instances you will start, this effectively makes every Cloneable Main.vi a shared clone reentrant VI.

What you're seeing is LabVIEW allocating (preparing) a pool of clones when launching instances of Shared Clone reentrant VIs. You are not seeing instances of Cloneable DQMH modules.

Courtesy of Jonathan Graesser: Usually the last instances in the lists are the Cloneable instances which are actually running. When things go wrong and the API Tester cannot find them anymore, you can open the front panel of those clones and stop them using the Abort button.

The number of clones shown - i.e. the size of the clone pool - depends mostly on the number of CPU cores available on your machine.

---