IRC5 ScreenMaker APP memory leak handling

anreten93

Hi everyone,

I'm working for a company project on an application for the FlexPendant that could be used by an operator for different tasks.

For this purpose, I'm using ScreenMaker in order to realize the app in an easier programming strategy. Either way, passing the time, the application is revealing no more trivial, computing a lot of operations by communicating with RAPID proc and than the user can navigate through various views with different graphical control objects.

I can imagine that this kind of application may cause problems in memory with the passing of time and after some hours in testing the app the overall performance falls down and system slows down. I supposed this was due to memory leaks somehow.
I read about the Dispose method for the FlexPendant SDK application, but I'm wondering if there is a way to avoid the memory problems by using ScreenMaker directly.

Are memory leaks handled in someway by Screenmaker? how can I avoid crashing the performances?

Thanks in advance!

mandolas

Hi ...

ScreenMaker applications tend to be very good for the user, but carelessness in development can indeed cause delays in the application.

Each instantiated window remains in memory and overloads the system.

Ex1: HOME->CONFIG->HOME considers 3 instances.

When navigating from one window to another, the previous one must be 'destroyed' so that only one instance of this window will be stored in memory.

Ex2: HOME->CONFIG->HOME only 1 instance.

The problem with Ex2 is that loading the window becomes slow, so you should pay attention to a property of the window that serves to keep it in memory.

I don't remember the property and I don't have the ScreenMaker option.

Today we configure PLC HMIs that are more robust and better meet our needs.

I hope I have contributed in some way.

Good work.