Re: Would this leak be inside gtk?

[Edscott Wilson <edscott wilson garcia gmail com>]

I've just verified with tcmalloc that there is no leak in
gtk_combo_box_new_with_entry(), on x86. The issue is with Valgrind which
gets confused with concurrent threads.  Although the spaguetti output pprof
is a bit confusing at first, once you look through the documentation the
diagrams are very helpful.

Issue solved.

Thanks.

2013/1/23 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.
> _______________________________________________
> gtk-app-devel-list mailing list
> gtk-app-devel-list gnome org
> https://mail.gnome.org/mailman/listinfo/gtk-app-devel-list