LabVIEW 2025Q3 .NET core memory leak!

[jyoung8711]

This is consistent even with built-in .NET functions.

See the attached VI where it's just generating some GUIDs.

It takes almost 2 orders of magnitude to run the .NET Core version.

You can see the memory drift as well if you have Process Manager open.

[Quiztus2]

---

@jyoung8711 wrote:

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

---

According to patch notes memory leak got already fixed with latest patch Bug Fixes 26Q1 

[jyoung8711]

---

@Quiztus2 wrote:

---

@jyoung8711 wrote:

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

---

According to patch notes memory leak got already fixed with latest patch Bug Fixes 26Q1 

---

There's another post about this where someone from R&D (I think) chimed in and said they thought it was fixed, and that they did some memory optimization... I think they missed the core issue though 😞 

The patch notes were not posted when I did my initial testing.

[Cloedu72]

I’ve finally had time to test the memory leak issue again.
=> The problem is still there 😞
The memory leak is slightly less severe, but it’s still there. Come on, NI!!!!!!!!!!!!!!

What can I say? Does NI understand the "definition of done"?

[billko]

---

@Cloedu72 wrote:

I’ve finally had time to test the memory leak issue again.
=> The problem is still there 😞
The memory leak is slightly less severe, but it’s still there. Come on, NI!!!!!!!!!!!!!!

What can I say? Does NI understand the "definition of done"?

---

Sometimes you think it's fixed but it's not. If you are a CLA you should know this.

[GregFreeman]

---

@jyoung8711 wrote:

This is consistent even with built-in .NET functions.

See the attached VI where it's just generating some GUIDs.

It takes almost 2 orders of magnitude to run the .NET Core version.

You can see the memory drift as well if you have Process Manager open.

---

Unrelated and a complete sidenote, but NewGuid is a static method and does not require a constructor node.