04-13-2026 04:30 PM
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.
04-16-2026 04:14 PM
@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
04-16-2026 04:46 PM
@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.