We encountered a handle leak/memory leak using OPCLabs QuickOPC DA in .NET.
The code is written in VB.NET.
Once we reference "OpcLabs.EasyOpc.DataAccess" anywhere in the code (instantiating a "EasyDAClient" of even just setting a parameter) the standard timer "System.Threading.Timer" starts leaking handles about linearly with the timer-frequency.
To observe the problem I stripped the application to the bare foundations.
The timer calls a sub that only executes:
Console.WriteLine("HandleCount: " & System.Diagnostics.Process.GetCurrentProcess().HandleCount)
Nothing else, but it there is still a handle leak implying a memory leak (resulting in 100% RAM usage after a while).
Is there any known issue with this?
You will find the stripped down version of the code in attachment + a screenshot of the referenced dll's.
There is no handle leak if everything reffering to OPCLabs is commented out.
Once any of the OPCLabs-lines is enabled again the memory/handle leak appears.
(e.g. line 15, 16, 23 ,24 or 25)
I use QuickOPC-5.35 (specifically build 5.35.442.1)
(A valid license was obtained for QuickOPC 5.22-5.3x Standard, with maintenance untill 23-11-2017)
The code is written in VB.NET.
Once we reference "OpcLabs.EasyOpc.DataAccess" anywhere in the code (instantiating a "EasyDAClient" of even just setting a parameter) the standard timer "System.Threading.Timer" starts leaking handles about linearly with the timer-frequency.
To observe the problem I stripped the application to the bare foundations.
The timer calls a sub that only executes:
Console.WriteLine("HandleCount: " & System.Diagnostics.Process.GetCurrentProcess().HandleCount)
Nothing else, but it there is still a handle leak implying a memory leak (resulting in 100% RAM usage after a while).
Is there any known issue with this?
You will find the stripped down version of the code in attachment + a screenshot of the referenced dll's.
There is no handle leak if everything reffering to OPCLabs is commented out.
Once any of the OPCLabs-lines is enabled again the memory/handle leak appears.
(e.g. line 15, 16, 23 ,24 or 25)
I use QuickOPC-5.35 (specifically build 5.35.442.1)
(A valid license was obtained for QuickOPC 5.22-5.3x Standard, with maintenance untill 23-11-2017)