@MTrivedi wrote:
Hi, everyone!
I'm trying to connect MVTec Halcon 11.0.1 software with LabVIEW 2011 and got one annoying bug. I have created very simple DLL in Visual Studio 2017 (C++) and then inserted it in LV through Call Library Function Node.When I push Run button everything goes ok. But when I try to close current VI or whole LabVIEW, the program just freezes/hangs up and stops responding to any activity.
Why are you copy-pasting my own messages? That doesn't make things better at all.
Today I've checked this issue on my machine with LV 2016, Halcon 12.0.2 and MSVS 2005. Well, I see the same message on closing VI:
HALCON error #9700: More than one user thread still uses HALCON resources during finalization
I suspect that something has changed in Halcon threading mechanisme since 11 version, so playing with thread pool doesn't work as expected. You have several options:
1) Contact MVTec support to assist you with this issue;
2) Switch to .NET assemblies instead of CLFNs;
3) Call LoadLibrary in the very beginning of your program (before calling any Halcon-related libraries). In the end you shouldn't call FreeLibrary. That would make LabVIEW to retain your DLL from unloading on VI close so it would be unloaded only on LV exit.
