OK that's good to know. The programmer was just about to start working on that, so many thanks for letting me know in time.

It is weird that an antivirus could be responsible for something like that, but one never knows...

Regards

Thank you. We will attempt to reproduce the issue here.

One more question: What data type are your items? Are they integers, floats, or also strings and other more complex types?

Best regards

OK, thank you. This means that the GC is being called regularly.

Which version and build of QuickOPC are you using? Hint: In File Explorer, right-click on one of the "OpcLabs.*" assemblies, select Properties, and take the info from the Details tab.

Thank you

I had a quick look at your code and I do not see anything wrong.

There is a possibility, however, that there is nothing wrong with the increasing memory consumption either. Running this service requires continuous creation of objects, and .NET only disposes of the memory when it runs the garbage collector. It would be OK for the memory to grow if the garbage collector has not run. I agree it would be somewhat strange that it did not run for 2 days or so, but it is something that needs to be clear first.

Please run PERFMON together with your process, and add following Counters for the instance of your process:

.NET CLR Memory -> # Gen 0 Collections
.NET CLR Memory -> # Gen 1 Collections
.NET CLR Memory -> # Gen 2 Collections

Let it run, and observe whether the counters increase and how often.