‎12-11-2025 03:15 AM
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. 😞
‎12-12-2025 08:40 AM
Does it help if I tell you that .Net Framework is not free of bugs either?
‎12-12-2025 10:34 AM
@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?
‎12-12-2025 03:35 PM
@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.
‎12-14-2025 02:19 AM
@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
‎12-18-2025 03:37 AM
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?