Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Peter_S_8
Beginner
73 Views

Kernel resource leak

Hello there

when I close my application the inspector throws me a kernel resource leak message pointing to the main window handle.

The summary screen shows two times the CreateWindow line.

The application has been cosed correctly with a DestroyWindow.

How can I get rid of that message??

kind regards

 Peter

0 Kudos
4 Replies
SergeyKostrov
Valued Contributor II
73 Views

>>The summary screen shows two times the CreateWindow line. >> >>The application has been cosed correctly with a DestroyWindow. >> >>How can I get rid of that message?? Could you post a screenshot with Inspector XE error? Also, I assume that you're dealing with a problem in GUI Win32 application. In that case, you need to review all calls to GDI Win32 API functions. Take into account, that even if the window for the application was successfully destroyed that window could have a menu resource allocated dynamically in the application. However, this is only a possible case and it is Not proven since your description is too generic. In overall, All GDI resources allocated dynamically need to be released before application exits.
Peter_W_Intel
Employee
73 Views

>>How can I get rid of that message??

Before doing memory error analysis, in "Configure Analysis Type" windows, uncheck "Detect resource leaks" option. That will be fine.

If GDI resource used in your program was not grown quickly, it is not the critical issue; If it happened in 3rd-party library, you have no idea to deal with; If your program runs shortly, when your process exits, MS will release all occupied resource. They are all I assumed:-)

In general speaking, as Sergey commented that you need to find why via call stack info

Peter_S_8
Beginner
73 Views

Thanks for your help

I have found embedded fonts as the cause of the message - they were not released on program exit.

kind regards

 Peter

Bernard
Black Belt
73 Views

As Sergey pointed it out you should have been checked recursively all handles to window and also other GUI elements which have parent-child  relationship with the top container which is window.

Reply