LabVIEW 2026Q1 still has the .NET Core memory leak

[Quiztus2]

😂

[Quiztus2]

---

@knischal43 wrote:

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

---

26Q3 still leaking

[pawhan11]

Thanks for super fast check!

[pawhan11]

Checked on my end with simple example and memory still grows.

[jyoung8711]

So, I just updated and tested this as well.

I will say, that compared to the previous version, the memory leak is MAJORLY improved.

Running for 100k GUIDs got me an average of ~60 bytes per GUID.

In the last version, 2026 Q1 (patch 2), the usage was ~720 bytes per GUID.

In 2025 Q3 (patch 4) the usage was ~4050 bytes per GUID.

While not "solved" I do think this is considerably improved (thankfully).

I have a few other things I need to test here to see if this version fixes some other known issues... we're at least getting closer.

[jyoung8711]

Ok, so (somewhat off topic) I had a chance to test some of the other outstanding issues:

- The method browser seems to be working correctly now

- The "crashing" issues related to optional parameters on methods seems to be resolved (https://forums.ni.com/t5/LabVIEW/State-of-Net-Core-in-2025Q3-Bugs-and-Errors/m-p/4457934/highlight/t...)

I still have a dependency issue described here: https://forums.ni.com/t5/LabVIEW/NET-Core-in-LabVIEW-2025-Q1/m-p/4421000 where the framework loads the wrong version of dependencies if the versions are newer than what's installed in windows.

[pawhan11]

Tried today on our larger app and .net8 in LV is still not usable i production. When there is a lot of .net code called and complex structures are passed memory grows very fast.

.net48 has no memory leaks and calls execute much faster. net8 leaks and app hangs on net8 calls for multiple milliseconds.Not to mention net8 has eol in november.