LabVIEW 2025Q3 .NET core memory leak!

[Cloedu72]

I am really disappointed. To date, I have not received any solution to this problem from NI. A memory leak of this magnitude is a show stopper!

I hope that someone from NI will respond to this thread and provide a concrete statement on the planned solution to the problem. 😞

[Quiztus2]

Does it help if I tell you that .Net Framework is not free of bugs either?

[santo_13]

---

@Quiztus2 wrote:

Does it help if I tell you that .Net Framework is not free of bugs either?

---

In fact, almost every software in this world has bugs. Ever wondered why every software keeps getting updates and when updates are stopped, it is a big thing?

[Frozen]

---

@santo_13 wrote:

... when updates are stopped, it is a big thing?

---

I thought that was because all the bugs have finally been fixed and now SW is safe to use.

[Quiztus2]

---

@santo_13 wrote:

---

@Quiztus2 wrote:

Does it help if I tell you that .Net Framework is not free of bugs either?

---

In fact, almost every software in this world has bugs. Ever wondered why every software keeps getting updates and when updates are stopped, it is a big thing?

---

Do you refer to the end of support for Core 8, which is in fact next year? https://learn.microsoft.com/de-de/lifecycle/products/microsoft-net-and-net-core

[Cloedu72]

Wow, what a shame! We just received LV2025Q3 Patch3 and the .NET memory leak still exists!
=> Come on NI, when can we expect a corrected version for this serious bug?

[pawhan11]

Thanks for checking this out, i was about to do the same.

Having high hopes for 2026 Q1 release, we might get a chance to have working .net8 in LabVIEW before it reaches end of life in November 2026 🙂