Hello,

we are using NLog in many applications without problems.
It seems that creating an instance of EasyXXClient has a big influence on the process and/or the memory management of .NET.

Can you provide some information, what's happening inside the Client:
- Is there any periodic processing started?
- Does it call the Garbage Collector?
- Is there any periodic allocation of memory even if there is no other OPC communication ingoing?

Any help is welcome.
Thank you
Peter

Hello,

we are experiencing an increasing memory usage of a process that uses QuickOPC and performs continous logging.

I have enclosed a sample program which creates an instance of EasyUaClient and starts logging into the file system.
There is no more OPC communication active, just creating the instance is enough to observe the increasing memory.
When running our OPC Client we see a constant increase in private bytes. After about 2-4 weeks of uptime the process is killed by the operating system, because the system runs out of memory.

The output of "Performance Monitor" for a short observation period of 16h is enclosed: red line = Number of private bytes of process; dotted line = Number of .NET CLR bytes

We have experienced this behaviour in these environments:
- Windows Server 2016
- Happens in both cases, using an instance of EasyDAClient or EasyUAClient
- Happens when building the sample using .NET 4.7.2
- Using QuickOPC 5.61 as well as using our licensed release 5.58
- Logging into file system must be active

We did not see this behaviour:
- Windows 10
- WIndows Server 2019
- Create an instance of EasyDAClient and build the sample using .NET 4.6.1
- Switching off logging
- if there is no instance of EasyDAClient or EasyUAClient

Out customers are using WIndows Server 2016 so we have to find a solution for this problem.

Thank you
Peter