Professional OPC
Development Tools

logos

lupa

Online Forums

Technical support is provided through Support Forums below. Anybody can view them; you need to Register/Login to our site (see links in upper right corner) in order to Post questions. You do not have to be a licensed user of our product.

Please read Rules for forum posts before reporting your issue or asking a question. OPC Labs team is actively monitoring the forums, and replies as soon as possible. Various technical information can also be found in our Knowledge Base. For your convenience, we have also assembled a Frequently Asked Questions page.

Do not use the Contact page for technical issues.

  1. Forum
  3. Discussions
  5. QuickOPC-Classic in .NET
  7. General Issues, Building
  9. EasyDAClient Memory Leak.

EasyDAClient Memory Leak.

More
05 Dec 2022 19:06 #11298 by IRuiz
EasyDAClient Memory Leak. was created by IRuiz
Hello, we are having critical issues with a never ending memory leak after recreating EasyDAClient objects.

NuGet: OpcLabs.QuickOpc 5.63.246
Target: TopServer 6.8 (Default installation, no custom tags created)

Attached to this case there is C# .NetFramework 4.7 example.

- While running in Debug x64 inside VS2019, leak is noticeable every time TopServer is manually reinitialized (Screenshot inside attached .Zip file)
- While running Release x64 outside VS2019, leak is noticeable all the time, never ending memory growth.
- Have seen memory grow from 70Mb to more than 5 gigs crashing or test VM. (Screenshot inside attached .Zip file)

Expected behavior:
- Memory should be released upon calling EasyDAClient Dispose(), or at least at some near point.
Attachments:

Please Log in or Create an account to join the conversation.

Moderators: support
  1. Forum
  3. Discussions
  5. QuickOPC-Classic in .NET
  7. General Issues, Building
  9. EasyDAClient Memory Leak.
Time to create page: 0.043 seconds