HomeSupportSystemDefinition .NET Object Is Not Released After Closing the Reference

SystemDefinition .NET Object Is Not Released After Closing the Reference

Updated Aug 9, 2018

Reported In

Reported In shows products that are verified to work for the solution described in this article. This solution might also apply to other similar products or applications.

Software

LabVIEW

VeriStand 2015

Issue Details

I need to operate on .nivssdf files from LabVIEW application using NationatInstruments.VeriStand.SystemDefinitionAPI(15.1.0.0) .NET assembly. I use .NET constructor SystemDefinition(String nivssdfFile) to load System Definition file and then Close Reference" to unload it. I noticed that after creating EXE application .NET object is not unloaded properly after using Close Reference. It cause that memory usage is increasing drastically.

Solution

This behavior was observed for Veristand 2015. It’s known that in Veristand 2017 this problem was fixed and after upgrading your project to this version the problem will not appear anymore.