Memory Leaks after displaying designer

[scotty]

I am using a memory-profiling tool (.NET Memory Profiler) to find possible memory leaks in my application. Doing so, I encountered a severe problem when working with Stimulsoft-Reports (Version 2019.2.3.0).
When displaying the designer with the simple code segment below and then closing it by clicking the close button, the memory profiler detects some Stimulsoft-Reports objects that remain in memory (see attached profiler screenshots). The object left behind multiply each time I re-open the designer.

Code: Select all

StiReport stiReport = new StiReport();            
stiReport.Design(false, this);

Can you help me with this problem?

[Lech Kulikowski]

Hello,

We recently investigated this problem.
Some optimizations were made and in the 2019.4.x build, according to our tests, memory leaks were almost halved. Unfortunately, nothing more to be done so far, then a global redesign of the UI library is required.

Thank you.