Valgrind reports lost memory at FcPatternObjectInsertElt. Here's part of the output, it repeats this several times: ==32454== 1,084 (384 direct, 700 indirect) bytes in 1 blocks are definitely lost in loss record 14,813 of 16,061 ==32454== at 0x48CC046: realloc (vg_replace_malloc.c:525) ==32454== by 0x9189346: FcPatternObjectInsertElt (fcpat.c:358) ==32454== by 0x9189D9C: FcPatternObjectAddWithBinding (fcpat.c:507) ==32454== by 0x918A4EB: FcPatternObjectAdd (fcpat.c:537) ==32454== by 0x91868FE: FcFontRenderPrepare (fcmatch.c:425) ==32454== by 0x9186989: FcFontMatch (fcmatch.c:553) ==32454== by 0x79031DD: pango_fc_fontset_get_font_at (pangofc-fontmap.c:761) ==32454== by 0x79035B1: pango_fc_fontset_foreach (pangofc-fontmap.c:1003) ==32454== by 0x7E4E1C2: pango_fontset_foreach (pango-fontset.c:101) ==32454== by 0x7904063: pango_fc_font_map_load_font (pangofc-fontmap.c:1678) ==32454== by 0x7E4D56E: pango_font_map_load_font (pango-fontmap.c:94) ==32454== by 0x7E4A56E: pango_context_load_font (pango-context.c:291) ==32454== ==32454== 1,084 (384 direct, 700 indirect) bytes in 1 blocks are definitely lost in loss record 14,814 of 16,061 ==32454== at 0x48CC046: realloc (vg_replace_malloc.c:525) ==32454== by 0x9189346: FcPatternObjectInsertElt (fcpat.c:358) ==32454== by 0x9189D9C: FcPatternObjectAddWithBinding (fcpat.c:507) ==32454== by 0x918A4EB: FcPatternObjectAdd (fcpat.c:537) ==32454== by 0x91867B7: FcFontRenderPrepare (fcmatch.c:416) ==32454== by 0x790300C: pango_fc_fontset_get_font_at (pangofc-fontmap.c:852) ==32454== by 0x79035B1: pango_fc_fontset_foreach (pangofc-fontmap.c:1003) ==32454== by 0x7E4E1C2: pango_fontset_foreach (pango-fontset.c:101) ==32454== by 0x7904063: pango_fc_font_map_load_font (pangofc-fontmap.c:1678) ==32454== by 0x7E4D56E: pango_font_map_load_font (pango-fontmap.c:94) ==32454== by 0x7E4A56E: pango_context_load_font (pango-context.c:291) ==32454== by 0x7E5181E: pango_layout_get_empty_extents_at_index (pango-layout.c:4374) ==32454==
False positive.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.