Re: Would this leak be inside gtk?

[Andrew Potter <agpotter gmail com>]

On Wed, Jan 23, 2013 at 1:38 PM, Edscott Wilson <
edscott wilson garcia gmail com> wrote:

> Maybe it's just a bug in Valgrind... I'm finding that a threaded
>  environment may confuse Valgrind. I'll do some more checking.

In Valgrind threads become serialized, there is no true concurrency.

I found a lot more success hunting memory leaks using Google's tcmalloc
library. To use the heapcheck feature, you'll need to run your program on a
x86 platform (a VM x86 on x86_64 works). tcmalloc on x86_64 does not
provide the requisite stack traces.