115586 2013-05-04 03:37:24 -0700 [GTK] Memory leaks in WebCore::FontCache::createFontPlatformData 2013-07-04 04:41:47 -0700 1 1 1 Unclassified WebKit WebCore Misc. 528+ (Nightly build) Unspecified Unspecified RESOLVED INVALID P2 Normal --- 0 elima webkit-unassigned magomez rego svillar oldest_to_newest 884521 0 elima 2013-05-04 03:37:24 -0700 Valgrind traces show memory being lost in WebCore::FontCache::createFontPlatformData when calling FcFontMatch() and not freeing the returned FcPattern. There are several traces with different stack paths, but all end with this pattern: ==28564== 1,424 (512 direct, 912 indirect) bytes in 1 blocks are definitely lost in loss record 6,376 of 6,599 ==28564== at 0x4C28CCE: realloc (vg_replace_malloc.c:632) ==28564== by 0x78B5A57: FcPatternObjectInsertElt (fcpat.c:358) ==28564== by 0x78B68E7: FcPatternObjectAddWithBinding (fcpat.c:507) ==28564== by 0x78B34B7: FcFontRenderPrepare (fcmatch.c:416) ==28564== by 0x78B36CC: FcFontMatch (fcmatch.c:553) ==28564== by 0x627F969: WebCore::FontCache::createFontPlatformData(WebCore::FontDescription const&, WTF::AtomicString const&) (in /opt/jhbuild/gnome3/checkout/WebKit/WebKitBuild/Release/.libs/libwebkit2gtk-3.0.so.0.21.0) 904622 1 magomez 2013-06-28 07:52:19 -0700 This seems to be a problem in fontconfig and not in WebKit. This very same issue was reported several times in its bugzilla (being this the last one https://bugs.freedesktop.org/show_bug.cgi?id=34208) and it seems to be a false positive and not a leak. 906135 2 svillar 2013-07-04 04:41:47 -0700 (In reply to comment #1) > This seems to be a problem in fontconfig and not in WebKit. This very same issue was reported several times in its bugzilla (being this the last one https://bugs.freedesktop.org/show_bug.cgi?id=34208) and it seems to be a false positive and not a leak. Indeed it was also closed as NOTABUG here https://bugs.freedesktop.org/show_bug.cgi?id=8215. There is an ongoing patch adding valgrind suppressions which already contains this false positive. Let's close this then.