On 14-02-14 08:02 PM, mathog wrote: > If pango induces fontconfig to allocate memory, but it never tells it to > release it, then that would explain valgrind entries like this: You are confusing still-allocated-and-reachable memory with leaks. Gtk+ caches lots of stuff, possibly Pango contexts, which cache cairo and fontconfig things, etc. Unless you can prove that no one above pango is keeping any Pango / cairo / fontconfig objects around, you can't expect those three pieces to fully clean up their caches. -- behdad http://behdad.org/ _______________________________________________ Fontconfig mailing list Fontconfig@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/fontconfig
