CEGUI (Crazy Eddie's GUI) Forums

No worries. I was just answering some of the questions. This isn't stopping any of my development. Thanks for the link to the Stack Overflow post. Using that instead of _CrtDumpMemoryLeaks() hides those reports and does report real memory leaks. Put one in deliberately to test. Thanks for the quick ...

Sorry for the late reply.

Ident wrote:

Code: Select all

 CEGUI::System::destroy();

Do you call this?

Yes, and it still reports leaks.

Additionally you must destroy your Renderer after you have destroyed your System

I saw this after I posted and tried that, but it still reports leaks.

Correct, the reporting is _CrtDumpMemoryLeaks(); Currently linking in CEGUIBase-0_d.lib CEGUICommonDialogs-0_d.lib CEGUICoreWindowRendererSet_d.lib CEGUIDirect3D11Renderer-0_d.lib CEGUIExpatParser_d.lib CEGUIFreeImageImageCodec_d.lib CEGUINullRenderer-0_d.lib So, no Lua and no Python. When I init, r...

Using a dynamically-linked 32-bit build in Windows 8 x64 with the Direct3D 11 renderer, doing nothing but bootstrapping on startup and calling CEGUI::Direct3D11Renderer::destroySystem() appears to cause memory leaks. No UI created, no system defaults set or anything. Just simple init and destruction...

Oh, and as an aside, the unresolved externals indicated in this thread involving CEGUI::FormattingSetting were still an issue, and the fixes prescribed in that thread fixed it. However, I didn't run into the PCRE issue, even though I built it and checked it in CMake. http://cegui.org.uk/forum/viewto...

I built CEGUI 0.8.4 with the dependencies package, 32-bit static using VS 2012 on Windows 8.0 x64, using D3D 11 as the renderer. I can build the sample framework as well as the modules. When I run the sample framework, I get an assert on startup. Here's the log and callstack. 24/08/2014 01:39:04 (St...