On Wed, 2005-04-27 at 06:22 -0400, Chris Capoccia wrote:
> so it looks like a small leak is present when all the fonts directories
> are traversed.
I'm fairly sure I know what this problem is and it should be fixed in
the final packages.
> the bug i reported is fixed. fc-cache -f no longer runs
so now i am re-running tests with the new packages you sent.
# valgrind --leak-check=full fc-cache -f -v
/usr/local/share/fonts/TrueType/B/
==5189== Memcheck, a memory error detector for x86-linux.
==5189== Copyright (C) 2002-2005, and GNU GPL'd, by Julian Seward et al.
==5189== Using valgrind-2.4
On Tue, 2005-04-26 at 16:50 -0400, Chris Capoccia wrote:
> i'm not sure whether this is a leak or a normal report, but the first
> subdirectory i picked finished and reported some data.
That's a leak, and one which I have been trying to fix. Did you manage
to install the newer version of fontcon
> Could you manage to run fc-cache on each directory separately until you
> find one which shows memory leaks?
>
> # valgrind --leak-check=full fc-cache -f -v /usr/local/share/fonts
>
> replacing /usr/local/share/fonts with suitable directories until you get
> leaks displayed?
i'm not sure whether
On Sun, 2005-04-24 at 07:23 -0400, Chris Capoccia wrote:
> it appears like the attatchements didn't make it onto the bug tracking system.
> i'll try again.
Ok, it looks like we haven't fixed the bug yet, and the output (as you
suggested) was truncated before any useful bits could be displayed.
Co
it appears like the attatchements didn't make it onto the bug tracking system.
i'll try again.==5085== Memcheck, a memory error detector for x86-linux.
==5085== Copyright (C) 2002-2005, and GNU GPL'd, by Julian Seward et al.
==5085== Using valgrind-2.4.0, a program supervision framework for x86-lin
Quoting Keith Packard <[EMAIL PROTECTED]>:
> Here's a .deb which should be pretty close to 2.3.2 when it does get
> released (your bug is blocking that).
>
> Please run your usual tests and see if it runs out of memory, even
> better would be to run
>
> valgrind --leak-check=full fc-cache -f
>
> a
> Could I get you to give the CVS version a try and see
> if it still has trouble on your machine? I can ship
> you a .deb if you'd rather have that to test with.
CVS would be OK if you provided step-by-step directions. I don't feel confident
enough that I could get things going properly with ju
On Thu, 2005-04-21 at 07:17 -0400, Chris Capoccia wrote:
> fc-cache runs out of memory when it is run with the -f option. I have a
> lot of TrueType fonts (more than 1000). fc-cache is able to run without
> errors
> when the -f option is not used.
I found a couple of leaks; one in fontconfig a
Package: fontconfig
Version: 2.3.1-2
Severity: important
fc-cache runs out of memory when it is run with the -f option. I have a
lot of TrueType fonts (more than 1000). fc-cache is able to run without errors
when the -f option is not used.
I have 512MB of RAM on this computer.
-- System Infor
10 matches
Mail list logo
