LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

LabVIEW 2026Q1 still has the .NET Core memory leak

I already detected the memory leak in LabVIEW (32bit) version 2025Q3 and opened a ticket. I received confirmation (via R&D) that the problem should be fixed in the official LV2026Q1 version.

Sorry NI, the problem still exists and could have been tested with my super simple VI. I don't know what else to say to our customers about this. Will it perhaps be fixed next year?

This is about trust and reliable systems. I don't see either of those at the moment.

 

Claude

 

Cloedu72_1-1770650798549.png

 

 

Cloedu72_0-1770650514036.png

 

https://forums.ni.com/t5/LabVIEW/LabVIEW-2025Q3-NET-core-memory-leak/m-p/4456862

CLA / CTD
Message 1 of 8
(458 Views)

Yeah, I see this as a big concern... Makes it tough to use this feature in production 😞

0 Kudos
Message 2 of 8
(413 Views)

do you also see this kind of conduct with labview 64 bit and .net 64 bit, or is this due to the 32 bit versions?

0 Kudos
Message 3 of 8
(320 Views)

I have only tested it with 32-bit.

CLA / CTD
0 Kudos
Message 4 of 8
(297 Views)

I can confirm that this is still a bug for 64-bit as well -- tested with this example

Message 5 of 8
(257 Views)

Got kudoing disabled in this thread? 😄

Actor Framework
0 Kudos
Message 6 of 8
(237 Views)

@Quiztus2 wrote:

Got kudoing disabled in this thread? 😄

 


 a temporary bug, I guess 😉

0 Kudos
Message 7 of 8
(205 Views)

Apologies for the inconvenience caused, we will shortly provide a patch for this issue in LV2026. 

 
Message 8 of 8
(111 Views)