Re: GTK+ is not Valgrind-friendly

On Thu, 2004-04-29 at 20:41, Paul Pogonyshev wrote:
> Hi.
> I'm developing an application that uses GTK+ for GUI part.  I find Valgrind to
> be very useful in detecting memory access errors and leaks.  However, GTK+
> leaves lots of unfreed memory at process termination, which makes Valgrind
> output for a GTK+ application way less usable and clean.  I have about 1 MB of
> unfreed memory in about 140--150 loss records after a typical run of my program.

A) Note that Valgrind also has *useful* leak detection output that does
   conservative GC to find unreachable memory.
B) See the mailing list thread linked to from for discussion.

But basically, I don't think a gtk_free_all_memory() is interesting;
it's a lot of extra bookkeeping for no actual benefit to apps.


Attachment: signature.asc
Description: This is a digitally signed message part

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]