Bug 5 - unending memory allocation?
Summary: unending memory allocation?
Alias: None
Product: fontconfig
Classification: Unclassified
Component: library (show other bugs)
Version: 2.1
Hardware: Other other
: high normal
Assignee: Keith Packard
QA Contact:
URL: http://bugs.debian.org/cgi-bin/bugrep...
: 6 19 (view as bug list)
Depends on: DEMO_1
  Show dependency treegraph
Reported: 2003-01-12 11:40 UTC by Colin Walters
Modified: 2016-10-14 11:35 UTC (History)
2 users (show)

See Also:
i915 platform:
i915 features:


Description Colin Walters 2003-01-12 11:40:59 UTC
As you can see in the above URL, someone filed a bug against the Debian
fontoconfig package saying that fc-cache consumed a lot of memory.  I can't
reproduce this personally, but maybe the submitter will be able to give more
Comment 1 Keith Packard 2003-01-13 05:38:11 UTC
It would be nice to know if this is a problem on machines with more reasonable
amounts of memory; 132Meg isn't a huge allocation for todays machines.
Comment 2 Lionel Elie Mamane 2003-01-13 21:12:56 UTC
It is. I have 256MB of memory, and my system barely manages it: I have to exit
all other programs, and then it just manages it. If I have a normal working
session running, random programs start getting killed, and often the X server is
second in line... Very annoying when I forget to exit all other programs.
Comment 3 Keith Packard 2003-01-28 13:33:05 UTC
It appears (from reading the Debian bug) that this is a problem in freetype, not
fontconfig.  I'm going to set this to INVALID and see if someone can figure out
which underlying version of freetype is causing the problem.  I don't see
this on my Debian system.
Comment 4 Keith Packard 2003-01-28 13:33:48 UTC
*** Bug 6 has been marked as a duplicate of this bug. ***
Comment 5 Keith Packard 2003-02-05 18:35:06 UTC
*** Bug 19 has been marked as a duplicate of this bug. ***
Comment 6 Joel Madero 2013-09-24 22:18:57 UTC
*** Bug 68054 has been marked as a duplicate of this bug. ***

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.