I am trying to investigate a memory leak in a quite complex application. I have used about 10 different profiling tools and .NET Memory Profiler seems to fit best.
I started the guided profiling "Investigate memory leaks", performed the operation that I consider to be the memory leak and took a snapshot. Then I performed the operation again and took another snapshot.
I found the form "FrmCvBlobInspection" which I think is the problem. I just don't really know how to go on from here. I displayed the type details of this form but the instances graph is really big and overwhelming, even if I highlight and align the root path. Could you please provide me with some help to solve those memory leaks?
Thank you in advance for any advice.
edit: The upload of my session file does not seem to have worked, therefore I provide you with the session file at
The ToolStrip instances are created in the method SysconaDisplay.InitializeComponent. If the SysconaDisplay instance is properly disposed, then the ToolStrip instances will also be disposed. Since you have SysconaDisplay instances that are kept alive by only EventHandlers, I assume that the instances are no longer in use. I recommend that you make sure that the SysconaDisplay instances, and other form instances, are properly disposed. This will hopefully make sure that you no longer have a memory leak.
As I mentioned above, the ToolStrip event handlers are updated when the Visible property is updated, but this VisibleChanged event is always not reliably invoked. You can read more about it in this article.
SciTech Software AB
with your help and the help of your tool I actually did find our memory leak and was able to close it. Thank you very much for this great tool and even more for your effort!
Users browsing this forum: No registered users and 18 guests