07-28-2016 09:36 AM - edited 07-28-2016 09:46 AM
Hi all,
we have a large LabVIEW application using .NET framework based assemblies (DLL files) for data storage and communication. In certain scenarios, where loads of .NET objects are to be created and accessed by LabVIEW, we're running into a situation that LabVIEW stops execution and is halted completely. At this point, we're able to still create new VIs etc. but as soon as the code tries to access any kind of .NET node (e.g. one simple System.Object constructor), this VI is halted also immediately and cannot be continued, stopped or aborted in any way. What is going on here?
We have reported problems with using huge numbers of .NET references to NI before (the internal pool of usable references is limited!) and this seems to be related somehow. Unfortunately, we have no solution for our problems so far. Therefore any help is greatly appreciated.
Kind regards,
Hans
07-28-2016 10:08 AM
Hans,
so the issue does not occur if you have only a couple of assemblies (and references) in memory?
Also please make sure that the assemblies do not have blocking loading callbacks included. It could be a race condition on the UI thread.
Norbert