From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
05-06-2020 02:48 AM
Hello,
I am trying to handle a Thorlabs motorized actuator by simple VI with a .NET container.
And I am in trouble to handle memory leakage even if I close all references that I used.
I tried to close all references that I've used, as you can see a screenshot of block diagram below.
I wrote this VI in LabVIEW 2019(64 bit) with saving for previous version(13.0), and copied the VI to another PC which LabVIEW 2013(32 bit) has been installed.
In a PC with LV 2013, the total consuming memory of LabVIEW increases by ~200MB, every time I call this VI.
However, I am confused because it was okay in another PC with LV 2019 - the memory increases by ~200MB, but when the running is finished, the memory went back to normal.
Solved! Go to Solution.
05-06-2020 04:38 PM
Just a wild guess, but maybe different .NET versions?
05-06-2020 11:56 PM
Thank you for your answer, but unfortunately it wasn't a clue.
I checked both PC's .NET framework versions and these are exactly same.
05-08-2020 01:17 AM
I rewrote my VI with APT programming(ActiveX communications), and the memory usages look fine for both computers.
Thank you all! 😀
05-08-2020 09:46 AM
Sorry I wasn't of more help. 😞
Glad you found a solution, though. And thanks for marking your own post as the solution so other forum members can benefit from your experience! 🙂