Comment #24 on issue 9245 by eisin...@google.com: Valgrind reports Fontconfig memory leaks http://code.google.com/p/chromium/issues/detail?id=9245
I traced the leak, and there are two sources of leaks here. One is that test_shell does not execute FcFini. Adding this function call already frees most of the leaks that result into this specific valgrind trace. The second source is within pango. There are static variables pointing to fontmap resources, e.g. in pangocairo-fontmap.c:pango_cairo_font_map_get_default. In the case of test_shell, the static variable default_font_map already holds references to all remaining leaks that result into the valgrind trace mentioned here. I guess there's nothing what we can do about the latter. I'd suggest to add the FcFini call, although that won't free all fontconfig resources. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings -- Automated mail from issue updates at http://crbug.com/ Subscription options: http://groups.google.com/group/chromium-bugs
