Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 164248 - <media-libs/freetype-2.2 causes memory leak on xpdf-based software
Summary: <media-libs/freetype-2.2 causes memory leak on xpdf-based software
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: High major (vote)
Assignee: Gentoo Security
URL:
Whiteboard:
Keywords:
Depends on: 173804
Blocks:
  Show dependency tree
 
Reported: 2007-01-28 15:39 UTC by davide.angelocola
Modified: 2007-07-06 08:52 UTC (History)
4 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
valgrind output with freetype 2.1 (with-freetype-2.1.log,26.96 KB, text/plain)
2007-01-28 15:41 UTC, davide.angelocola
Details
valgrind output with freetype 2.2 (with-freetype-2.2.log,17.61 KB, text/plain)
2007-01-28 15:43 UTC, davide.angelocola
Details
freetype eating everything (kpdf.png,81.13 KB, image/png)
2007-05-05 14:59 UTC, Paolo Ornati
Details

Note You need to log in before you can comment on or make changes to this bug.
Description davide.angelocola 2007-01-28 15:39:51 UTC
media-libs/freetype-2.1 contains a big memory leak. After emerging freetype-2.2
the leak disappeared.
Comment 1 davide.angelocola 2007-01-28 15:41:34 UTC
Created attachment 108378 [details]
valgrind output with freetype 2.1

The memory leak:
==12157== 97,950,488 bytes in 1,579 blocks are definitely lost in loss record 228 of 228
==12157==    at 0x4A1FAB0: malloc (in /usr/lib64/valgrind/amd64-linux/vgpreload_memcheck.so)
==12157==    by 0x7469A4F: ft_mem_qalloc (in /usr/lib64/libfreetype.so.6.3.8)
==12157==    by 0x746DED3: ft_mem_alloc (in /usr/lib64/libfreetype.so.6.3.8)
==12157==    by 0x746E982: ft_mem_qrealloc (in /usr/lib64/libfreetype.so.6.3.8)
==12157==    by 0x746E9F7: ft_mem_realloc (in /usr/lib64/libfreetype.so.6.3.8)
==12157==    by 0x74A30BD: (within /usr/lib64/libfreetype.so.6.3.8)
==12157==    by 0x74A3461: (within /usr/lib64/libfreetype.so.6.3.8)
==12157==    by 0x74A7F62: (within /usr/lib64/libfreetype.so.6.3.8)
==12157==    by 0x746E27B: FT_New_Size (in /usr/lib64/libfreetype.so.6.3.8)
==12157==    by 0x746F919: FT_Open_Face (in /usr/lib64/libfreetype.so.6.3.8)
==12157==    by 0x74702F3: FT_New_Memory_Face (in /usr/lib64/libfreetype.so.6.3.8)
==12157==    by 0x97C9D6E: SplashFTFontFile::loadTrueTypeFont(SplashFTFontEngine*, SplashFontFileID*, SplashFontSrc*, unsigned short*, int, int) (in /usr/kde/3.5/lib64/kde3/libkpdfpart.so)
Comment 2 davide.angelocola 2007-01-28 15:43:50 UTC
Created attachment 108380 [details]
valgrind output with freetype 2.2

the leak disapperead
Comment 3 Diego Elio Pettenò (RETIRED) gentoo-dev 2007-01-28 15:46:52 UTC
Foser, I suppose that this is the good moment to actually unmask the new freetype, if you fix the foobillard problem that has a patch already.

If you don't say anything in, say, 10 days, I'll see to discuss with printing herd about taking care of the issue ourselves.
Comment 4 Diego Elio Pettenò (RETIRED) gentoo-dev 2007-02-08 14:08:50 UTC
Freetype 2.2.1 is out of package.mask, will go stable after some testing.
Comment 5 Raphael Marichez (Falco) (RETIRED) gentoo-dev 2007-02-10 20:36:16 UTC
Reopening in the security team scope, thanks to Flameeyes who pointed me the bug.

Security team, do you consider this as a security issue? (DoS in a library)
In such case, we would hurry up the stabilization of freetype-2.2.1 and perhaps issue a GLSA...
Comment 6 Raphael Marichez (Falco) (RETIRED) gentoo-dev 2007-02-10 20:36:50 UTC
Security team, do you consider this as a security issue? (DoS in a library)
In such case, we would hurry up the stabilization of freetype-2.2.1 and perhaps
issue a GLSA...
Comment 7 Paolo Ornati 2007-05-05 14:59:46 UTC
Created attachment 118242 [details]
freetype eating everything
Comment 8 Paolo Ornati 2007-05-05 15:00:06 UTC
Please mark "freetype-2.3.4" stable soon... it fixes this annoying problem (just open a PDF with KPDF, scroll it up and down and you get swappiness / OOM killer!).

Maybe this screenshot explains it better ;)
Comment 9 Matija "hook" Šuklje 2007-05-09 12:29:22 UTC
So basically I should upgrade freetype and unmerge poppler?

Thanks so much for the explanation. I hope I haven't caused too much chaos and work :/
Comment 10 Ryan Hill (RETIRED) gentoo-dev 2007-07-01 21:29:58 UTC
all archs now have freetype-2.3 stable.  pinging security to close this bug.
Comment 11 Raphael Marichez (Falco) (RETIRED) gentoo-dev 2007-07-06 08:52:26 UTC
Closing this bug now it is fixed on all arches, noGLSA. Feel free to reopen if you disagree.