Hi,
How can I use TRACK_ALIVE_OBJECTS to search for memory leaks?

in the Noesis debugging build, on the call Noesis::Shutdown() I get the log

NOESIS[E]: Assertion failed: gFaceCache.Empty(), at VGLFontFace.cpp(294).
NOESIS: Noesis Shutdown.
NOESIS[W]: Memory leaks detected: 232560 bytes.
NOESIS: Enable 'TRACK_ALIVE_OBJECTS' in BaseObject.cpp to get more information.
NOESIS: Enable 'CRTDBG_LEAK_CHECK' in Memory.cpp to get more information.

Hi Tomas,

Those macros are available if you compile Noesis from source. If you don’t, you’ll need to implement your own leak detection mechanism using the memory allocation callback. If you’re using standard malloc in Visual Studio, you can use _CrtDumpMemoryLeaks().

Let me know if this helps.

Hi Tomas,

Those macros are available if you compile Noesis from source. If you don’t, you’ll need to implement your own leak detection mechanism using the memory allocation callback. If you’re using standard malloc in Visual Studio, you can use _CrtDumpMemoryLeaks().

Let me know if this helps.

Hi,
The NoesisGui sources are not available and _CrtDumpMemoryLeaks() does not help either((

first, I need to remove the assertion that occurs on Fonts Release.
inside Noesis::Shutdown(), perhaps this is the reason for the leaks.
What reason could this assertion have?

Hi Tomas,

Could you please provide a bit more context regarding the license you're using? Is this an evaluation license? I’m asking because I noticed you're using the symbol server, because you are getting clean call stacks.

If that’s the case, and you reimplement memory allocation using malloc/free, you should be able to use _CrtSetDbgFlag(_CRTDBG_ALLOC_MEM_DF) at initialization and _CrtDumpMemoryLeaks() on exit to get a list of memory leaks, along with their allocation IDs. If you then set _crtBreakAlloc to one of those IDs, it should trigger a debugger break the next time you run the game, allowing you to catch the allocation in real time. This is explained in the MSDN. It will only work if the IDs are the same with every execution though.

As for the asserts you’re seeing, they appear to be related to XAML nodes with font families that aren’t being released properly. These unreleased nodes are likely leaving font references in the global font cache.

Let me know if you need help digging further into this.

Could you please provide a bit more context regarding the license you're using? Is this an evaluation license? I’m asking because I noticed you're using the symbol server, because you are getting clean call stacks.

I have an Indie license.
In the release build, only the size of the leak is printed in the log.
The call stack I provided is a debugging build + .pdb

The leak was due to binding to the parent element in xaml.
This leak was not diagnosed before version 3.2.7

Do you have a minimal XAML example that reproduces this? I'd love to take a closer look

Do you have a minimal XAML example that reproduces this? I'd love to take a closer look

One RadioItem component can be bound to multiple controls, so I created a converter that generates a unique group name for each control. Otherwise, IsChecked will always be false.
This is a brief explanation of why I had to implement it like that.

The following line leads to a memory leak:
<Binding RelativeSource="{RelativeSource AncestorType={x:Type ItemsControl}}" />