10-16-2025 09:03 AM - edited 10-16-2025 09:41 AM
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)
a few minutes later.....
Is there a workaround, or will NI consider this a bug?
=> I did not observe the same behaviour with .NET Framework....
Claude
10-23-2025 12:42 AM
Any ideas or similar experiences? It seems as if no one is using .NET Core?
10-23-2025 04:36 AM
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.
10-23-2025 08:20 AM
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.
10-23-2025 03:11 PM
I think this is pretty concerning. 4 kB per call could definitely add up quickly.
10-24-2025 01:08 AM - edited 10-24-2025 01:09 AM
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!