Memory leak at API function "SoVariableCollection.ItemByName" at Engeneering Studio

• Related Articles

• calling the LicenseEntry::Values API method causes a memory leak

  Summary A memory leak in the API method LicenseEntry::Values was fixed, as well as a leak in the screen switch function of the report viewer Description A memory leak in the API method LicenseEntry::Values was fixed, as well as a leak in the screen ...

• Checklist: Engineering Studio cannot start or closes unexpectedly

  Time estimate: 30 minutes Please go through all the points in the following checklist. If necessary, confirm with IT Department any information you cannot verify before contacting your local COPA-DATA Representative. Checklist usage: #. [Quick hints] ...

• FAQ: How to hook to function execution in the Service Engine over the API?

  COM: RtFunctions contains a new event (PreExecuteFunction) which gets fired before a function is executed. This event handler contains a parameter which is a temporary copy of the function which is about to be executed. ADDIN: An identical event ...

• Checklist: Distributed Engineering – Engineering Studio cannot connect to the Project Database-Server / Elements cannot be checked-in/out

  Time estimate: 45 minutes Please go through all the items in the following checklist. If necessary, confirm any information you cannot verify with the IT department before contacting your local COPA-DATA representative.  Checklist usage: #. [Quick ...

• Addin Services seem to cause Memory leak

  Summary - Description - Information I suggested the customer to trigger a zenon function with a wizard inside the worker thread. Wizards do not have this issue since the appdomain is destroyed after finishing and the memory is released. I do not know ...