We are using the following setup.
OPC Quick Client v5.35.1173.1.
Wonderware inTouch for HMI
.NET Windows Forms application which references OPC Quick client.
We have been noting regular performance issues in production. Every two weeks or so, performance degradation is noted which leads to OPC event processing hang-ups in our .NET application we end up having to restart it.
What we have also noted is that there seems to be a handle leak stemming from use of the EasyDAClient object we use. From analysis, these leaks are coming from abandoned Mutex objects somewhere within the OPC code or in a dll which you use. This seems to conform to the below article.
The performance issues and hangups are quite subtle at times and sometimes our logs don't seem to give us too much information even though the performance of the system has significantly slowed and we need to restart it. I have provided some sample logs for you to assess. I have some questions in this regard:
1) Are the OPC client errors we are seeing directly related to the handle leak?
2) if not, can you provide any insight on the exception in question?
3) Are there any established symptoms of the handle leaks associated with the above referenced article on the leaks?
Sample OPC Client error message
Sample handle count snapshot of application. (Without handle leak it should run at about 500-600 handles).
Sample Mutant handle creation from Process Explorer
Sample abandoned Mutex information from WinDbg