Hi,

Picking up on this thread a little late.

We have noted a very similar handle leak when using QuickOPC-5.35. There is a consistent increase in abandoned Mutant Handles attributable to our .NET Windows Forms app which utilises the QuickOPCClient.

Can you provide further insight as to which pre-requisute installations map directly to the config entries you have suggested. Do we have to install ALL of the ones listed in the folder provided by OPC (C:\Program Files (x86)\OPC Labs\QuickOPC 5.3\Redist) or just a subset of them? I have attached a screenshot of the links to the available installations which are in the OPC Redistributables folder as well as the actual links themselves (one of the links appears to be dead also by the way).

1) That is C++ redistributable. That is clear
2) ?
3) ?

1: <add key="OpcLabs.EasyOpc.Native.Assemblies.EnableVC120RedistBoxer" value="false"/>
2: <add key="OpcLabs.EasyOpc.OpcPSBoxing.EnableOpcCodePSBoxer" value="false"/>
3: <add key="OpcLabs.EasyOpc.UA.Toolkit.UAClientEngineBase.EnableUACertificateGeneratorBoxer" value="false"/>


Available Links:
1) opcfoundation.org/developer-tools/developer-kits-classic/core-components/ DEAD LINK
1-A) opcfoundation.org/developer-tools/samples-and-tools-classic/core-components IS THIS THE CORRECT ALTERNATIVE??
2) www.opclabs.com/files/downloads/QuickOpc/5.35/OPC-UA-SDK-1.0...-Interop-Components-Redist.zip
3) opcfoundation.org/developer-tools/samples-and-tools-unified-...re/local-discovery-server-lds/
4) www.microsoft.com/en-us/download/details.aspx?id=40784


Thanks,

Johnny

Hello,

Thanks again for you quick response.

The following two keys:
<add key="OpcLabs.EasyOpc.OpcPSBoxing.EnableOpcCodePSBoxer" value="false"/>
<add key="OpcLabs.EasyOpc.UA.Toolkit.UAClientEngineBase.EnableUACertificateGeneratorBoxer" value="false"/>
don't seem to do much in our setup, they don't generate any errors but don't stop the problem either. It seems like they are not read and as such ignored (please correct me if I'm wrong).

The key <add key="OpcLabs.EasyOpc.Native.Assemblies.EnableVC120RedistBoxer" value="false"/> generates following error:

"An unhandled exception of type 'System.TypeInitializationException' occurred in Microsoft.VisualStudio.HostingProcess.Utilities.dll

Additional information: The type initializer for 'NS_IMCCommunication.Main' threw an exception."

It seems that the parameter is found but initialization fails. Do I do something wrong?

I will add the entire project in attachment for you reference.

Hello,

Thanks for your quick reply.

I added the application settings as stated in the article you provided ("kb.opclabs.com/How_to_disable_prerequisites_boxing").
For now this doesn't solve the problem.

Maybe I add them in a wrong way or it are indeed different setting-names for this version as you stated in your reply.
I added the current 'App.Config'-file as an attachment.

Kind regards,

JV

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)