LabVIEW 2026Q1 still has the .NET Core memory leak

[Cloedu72]

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

[jyoung8711]

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

[alexderjuengere]

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?

[Cloedu72]

I have only tested it with 32-bit.

[jyoung8711]

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

[Quiztus2]

Got kudoing disabled in this thread? 😄

[alexderjuengere]

---

@Quiztus2 wrote:

Got kudoing disabled in this thread? 😄

---

 a temporary bug, I guess 😉

[knischal43]

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

[Quiztus2]

Replacing 'To .Net Object.vi' and '.Net Object to Variant.vi' with Polymorphics was not wise. Compiling code for previous versions is now broken. Something that worked with other modules pretty well until now.
It would have been the better to choice just to add the  'To .Net Core Object.vi' and '.Net Core Object to Variant.vi' . Please revert adding Polymorphics.

[jyoung8711]

Just an FYI the latest patch : 26.1.1.49193-0+f41 (released this week did NOT fix this issue 😞 )