Bug 884536

Summary:	python/fontconfig/expat memory leak
Product:	[openSUSE] openSUSE 12.3	Reporter:	Bernhard Wiedemann <bwiedemann>
Component:	Basesystem	Assignee:	Charles Arnold <carnold>
Status:	RESOLVED WONTFIX	QA Contact:	E-mail List <qa-bugs>
Severity:	Normal
Priority:	P5 - None	CC:	chcao, pgajdos, puzel
Version:	Final
Target Milestone:	---
Hardware:	x86-64
OS:	openSUSE 12.3
Whiteboard:
Found By:	Development	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Bernhard Wiedemann 2014-06-26 11:16:56 UTC

after observing a virt-manager process that used 5+ GB of RAM,
I tried to track it down using
valgrind --log-file=/dev/shm/valgrind.virtmanager --leak-check=full --track-origins=yes /usr/bin/python "/usr/share/virt-manager/virt-manager.py"

and found

==24871== 3,168 (2,816 direct, 352 indirect) bytes in 11 blocks are definitely lost in loss record 12,210 of 12,615
==24871==    at 0x4C2C27B: malloc (in /usr/lib64/valgrind/vgpreload_memcheck-amd64-linux.so)
==24871==    by 0x13ED2DBB: FcPatternObjectInsertElt (fcpat.c:453)
==24871==    by 0x13ED3FC8: FcPatternObjectAddWithBinding (fcpat.c:644)
==24871==    by 0x13ED40B8: FcPatternAppend (fcpat.c:1120)
==24871==    by 0x13ED9291: FcEndElement (fcxml.c:2504)
==24871==    by 0x161744FF: doContent (xmlparse.c:2532)
==24871==    by 0x1617546D: contentProcessor (xmlparse.c:2105)
==24871==    by 0x1617977C: XML_ParseBuffer (xmlparse.c:1651)
==24871==    by 0x13ED87E0: FcConfigParseAndLoad (fcxml.c:2967)
==24871==    by 0x13ED8A8E: FcConfigParseAndLoad (fcxml.c:2832)
==24871==    by 0x13ED8F7C: FcEndElement (fcxml.c:2081)
==24871==    by 0x161744FF: doContent (xmlparse.c:2532)

question is if that is a problem in the library itself or in how it is used by the caller (i.e. python wrapper so)

Comment 1 Petr Gajdos 2015-01-05 08:30:05 UTC

12.3 is EOL.

Comment 2 Charles Arnold 2015-01-05 18:31:53 UTC

12.3 end of life.
You could try to dup it on 13.1