02-09-2026 09:30 AM - edited 02-09-2026 09:52 AM
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
https://forums.ni.com/t5/LabVIEW/LabVIEW-2025Q3-NET-core-memory-leak/m-p/4456862
02-09-2026 04:36 PM
Yeah, I see this as a big concern... Makes it tough to use this feature in production 😞
02-12-2026 04:12 AM
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?
02-12-2026 06:48 AM
I have only tested it with 32-bit.
02-12-2026 10:54 AM
I can confirm that this is still a bug for 64-bit as well -- tested with this example
02-12-2026 12:19 PM - edited 02-12-2026 12:19 PM
Got kudoing disabled in this thread? 😄
02-13-2026 04:50 AM
@Quiztus2 wrote:
Got kudoing disabled in this thread? 😄
a temporary bug, I guess 😉
02-17-2026 07:23 AM
Apologies for the inconvenience caused, we will shortly provide a patch for this issue in LV2026.