U++ framework: U++ community news and announcements » Linux GlCtrl leaks problem fixed, new leaks related functions

Home » Community » U++ community news and announcements » Linux GlCtrl leaks problem fixed, new leaks related functions

Show: Today's Messages :: Polls :: Message Navigator
E-mail to friend

Linux GlCtrl leaks problem fixed, new leaks related functions [message #57819]

Sun, 19 December 2021 15:01

mirek
Messages: 14291
Registered: November 2005

Ultimate Member

This was problem that was hunting us for years: With Linux radeon driver we got memory leaks warning no matter what we have tried.

Today I have finally found out why:

The problem is that those static leaks are allocated in different thread, so our attempts to ignore them using MemoryIgnoreLeaksBlock are not enough.

I have solved problem by adding

static bool Thread::IsUpp()

Calling thread was started using U++ Thread class (for main thread returns false).

void MemoryIgnoreNonMainLeaks()

Makes leaks detector ignore leaks by global constructors.

void MemoryIgnoreNonUppThreadsLeaks()

Makes leaks dectector ignore leaks created by threads that are not launched by U++ Thread class.

These get called from GLCtrl finally initialisation fixing the problem...

Another new function that can help to figure out leaks when leak breakpoints are not usable:

dword MemoryGetCurrentSerial()

In debug mode, returns the serial number of the next allocated block. This number is eventually listed in the log in case there are any leaks.

Returns the serial of NEXT block to be allocated. The idea is to find the leak using bisection (horribly tedious, but probably the option sometimes).

Report message to a moderator