RawDataContainer Debug Assertion Failed!

[ArmaDuck]

When I close my application in debug mode I get a Debug Assertion Failed! in CEGUIDataContainer.h.

File: dbgdel.cpp
Line: 52

Expression: _BLOCK_TYPE_IS_VALID(pHead->nBlockUse)

Stack trace:

Code: Select all

CEGUI.dll!CEGUI::RawDataContainer::release()  Line 141 + 0x18   C++
CEGUI.dll!CEGUI::RawDataContainer::~RawDataContainer()  Line 135   C++
CEGUI.dll!CEGUI::Font::FontImplData::~FontImplData()  + 0x2e   C++
CEGUI.dll!CEGUI::Font::FontImplData::`scalar deleting destructor'()  + 0x2b   C++
CEGUI.dll!CEGUI::Font::~Font()  Line 157 + 0x31   C++
CEGUI.dll!CEGUI::Font::`scalar deleting destructor'()  + 0x2b   C++
CEGUI.dll!CEGUI::FontManager::destroyFont(const CEGUI::String & name={...})  Line 136 + 0x36   C++
CEGUI.dll!CEGUI::Scheme::unloadResources()  Line 279   C++
CEGUI.dll!CEGUI::Scheme::~Scheme()  Line 150   C++
CEGUI.dll!CEGUI::Scheme::`scalar deleting destructor'()  + 0x2b   C++
CEGUI.dll!CEGUI::SchemeManager::unloadScheme(const CEGUI::String & scheme_name={...})  Line 93 + 0x36   C++
CEGUI.dll!CEGUI::SchemeManager::~SchemeManager()  Line 61 + 0x39   C++
CEGUI.dll!CEGUI::SchemeManager::`scalar deleting destructor'()  + 0x2b   C++
CEGUI.dll!CEGUI::System::~System()  Line 399 + 0x2d   C++

Using the latest OGRE and CEGUI CVS.
MSVC 7.1, WinXP Pro SP2.

This post had a similar problem:
http://crayzedsgui.sourceforge.net/modu ... opic&t=206

[CrazyEddie]

I'll check this out and get back to you...

[CrazyEddie]

Okay, the solution for the moment is to disable the memory manager in Ogre (which means a full recompile).

What is happening is that the memory is being allocated by Ogre via the Ogre memory manager, which is all good. The problem is that when the memory is released by the RawDataContainer object, the delete[] operator is not going through the Ogre memory manager and so you get the assertion.

It's possible that another solution may present itself, but for now this is all I have

CE.

[Spoke]

Ummm, we have the same problem.

If we find a solution I will post it here.

[CrazyEddie]

What version is this? The issue should be fixed; you need to update from CVS to get the fix (both head and release_0-10 have the fix applied).

CE.