When a runtime client requests a larger amount of archive data, e.g. for displaying a trend with many variables for a long time period from a base archive, the runtime on the client can close unexpectedly if there is insufficient free memory for decompressing the received archive data from the server.
When a runtime client requests a larger amount of archive data, e.g. for displaying a trend with many variables for a long time period from a base archive, the runtime on the client can close unexpectedly if there is insufficient free memory for decompressing the received archive data from the server.
An issue has been addressed in the runtime where a client could close unexpectedly when a large amount of archive data was received from the server, and the client had not enough free memory.
Now if the data received cannot be processed on the client due to insufficient free memory, the archive data is discarded and will not be displayed in the runtime. An error message will be logged in the diagnosis server: "NET Error during uncompressing. Out of memory. Packet is lost."
As a workaround the maximum amount of archive data that is sent from the server to a client can be limited by setting the zenon6.ini entry
[ARCHIV] SPEICHER=100000
This will limit the amount of memory to 100MB.
Also as a general recommendation, following archives should be configured. Data from the base archive should be displayed with a narrow time filter.