LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

LabVIEW 2025Q3 .NET core memory leak!

I have discovered that LabVIEW 2025Q3 has a .NET memory leak. It doesn't matter which method you call from any class, a few kilobytes are lost every time. When large amounts of data are transferred during the method call, it happens faster, but the underlying problem remains.

I tried explicitly calling the garbage collector in .NET, but that didn't help. Within a few minutes, the memory in LV2025Q3 32-bit fills up and an error message (Memory full) appears.
=> Memory leak of approximately 4.2 kB per call (current example)

I borrowed the example from a forum member who demonstrates the problem using a very simple example. (https://forums.ni.com/t5/LabVIEW/net-8-labview-2025/m-p/4433787)

 

Cloedu72_0-1760623922910.png

 

Cloedu72_0-1760624282689.png

 

Cloedu72_0-1760623541716.png

 

 

Cloedu72_0-1760622794462.png

a few minutes later.....

Cloedu72_1-1760622903886.png

 

Is there a workaround, or will NI consider this a bug?
=> I did not observe the same behaviour with .NET Framework....

Claude

CLA / CTD
0 Kudos
Message 1 of 6
(380 Views)

Any ideas or similar experiences? It seems as if no one is using .NET Core?

CLA / CTD
0 Kudos
Message 2 of 6
(181 Views)

What happens if you send the .NET reference through a shift register? I had a similar experience with an ActiveX program where too many calls caused a crash. In that case reusing the reference reduced the issues.

G# - Award winning reference based OOP for LV, for free! - Qestit VIPM GitHub

Qestit Systems
Certified-LabVIEW-Developer
0 Kudos
Message 3 of 6
(156 Views)

Yes, that leads to the same problem. I have tried almost everything in the real application. This is just a simple demonstrator that is reduced to the essentials.

CLA / CTD
Message 4 of 6
(140 Views)

I think this is pretty concerning. 4 kB per call could definitely add up quickly.

0 Kudos
Message 5 of 6
(114 Views)

I have also submitted a service request to NI. NI is currently working on this issue and the support has now forwarded it to R&D. Hopefully, the fix will be added in Patch3!

CLA / CTD
Message 6 of 6
(92 Views)