Fideling around with asynchronously calling reentrant VIs I observed following effect: after a single call of "Open VI Reference" with option "x40" (simultaneous reentrant calls) 5 clones of the reentrant VI to call showed up in the LabVIEW Taskmanager. This is easy to reproduce using the "Asynchronous Call and Collect" example shipped with LabVIEW:
- Change the order of elements in the "Pass option 0x40?" array on the left.
- Insert a breakpoint right after the call of "Open VI Reference"
- open "LabVIEW Task Manager"
- run the VI and refresh Task Manager view (F5)
I tested it with LV2014SP1 and LV2016 with the same result.
I'm curious, if this is wanted behaviour!? First I thought LV loads a bunch of clones for performance reasons. However a second call to "Open VI Reference" while the first asynchronously called VI is still running doesn't make use of the clones already in memory, but brings up another 5 of them.
In contrast using "Open VI Reference" with the old school option "x08" and the "Run VI"-InvokeNode only a single clone appears in the task manager.
