Forum

Hi,

I’m looking for the proper way to free/delete all the memory used by EnableCustomization(). When I call the following code, I get a bunch of memory leaks when shutting down.

if(!CCustomizeDlg::EnableCustomization(this,__ECSF_DEFAULT)) {
ASSERT( FALSE );
return -1;
}

Is there a shutdown function I should be calling in DestroyWindow()?

Thanks,
Mike

Problem solved.

Added AfxOleInit(); to the CApp::InitInstance() no more leaks. Not sure why this is the case, but it works great and the 1000’s of leaks are plugged.

Thanks for the help. Prof-UI is a great tool.

Mike

The OLE initialization is essential because the customization subsystem uses OLE drag-and-drop APIs for menu items and toolbar buttons. But this should have to do with memory leaks. We guess the source of these leaks was specific to your project only.

There are no API that would allows you deinitialize the customization subsystem directly. Everything should be closed and deallocated automatically. If you have memory leaks of MFC/Prof-UIS objects, there must be some problem in the application shutdown. For instance, it may be closed by the ExitThread() or PostQuitMessage() APIs so the destructors won’t be called. Please check if the DestroyWindow() virtual method of the main frame class and the ExitInstance() virtual method of application class are invoked at shutdown. You can also configure the debugger to break on any exceptions before shutdown and clarify what happens during shutdown. Any unhandled exceptions may also crash your application even without any popup message boxes.

Just a guess: Have you followed the steps described in the Feature Article Prof-UIS Customization Subsystem ? If so, can you reproduce the problem in any of the customized ProfUIS samples ( in BitmapEditor, for example )?