GetAlarmEntryCollection() unusual Memory Usage when called multiple times

GetAlarmEntryCollection() unusual Memory Usage when called multiple times

Summary

Some Add-Ins create memory leaks when called multiple times. A solution has been implemented for this.

Description

When certain Add-Ins are called multiple times, unusual memory usage occurs. The memory used is then not released again. This is due to the behaviour of the .Net Framework, which can lead to memory leaks during certain actions.

A workaround solution has been deployed for this behavior. This changes the loading behavior of Add-Ins Please also note the side effects of this solution!

Solution:

Configure the loading behavior of Add-Ins in zenon6.ini.

1. Open the zenon6.ini.

2. Search for or create the [ADDINS] section.

3. Configure the entry "LOAD_ADDINS_IN_DEFAULT_APPDOMAIN".

- 0: Add-Ins are loaded into private AppDomains

- 1: Add-ins are loaded into the default AppDomain

4. Activate the switch by setting LOAD_ADDINS_IN_DEFAULT_APPDOMAIN=1.

This forces the loading of Add-Ins into the default AppDomain and prevents memory leaks caused by .Net Framework.

Attention: This means that it is no longer possible to reload Add-Ins. Extensions and assemblies that are consumed by the loaded add-in can no longer be updated as long as the Service Engine is running.

To benefit from this fix:

  • Update your zenon Software Platform to the latest build of zenon 8.00 or higher.

 



Item ID: 255009
Version: 10.00 Build: 214128