[luatex] mkluatexfontdb devours memory

Arno Trautmann Arno.Trautmann at gmx.de
Sat May 11 12:03:36 CEST 2013

Hi all,

besides possible problems, I could work for now if the OS's fonts would 
not be loaded. Is it possible to blacklist a whole directory? In the 
documentation I only found blacklisting of single files.


Arno Trautmann wrote:
> Hi,
> Élie Roux wrote:
>> Hi,
>>> the output of
>>> luaotfload-tool --update --force --verbose=5 --log=stdout
>>> is available under
>>> http://justpaste.it/2lhr
>>> I stopped the program when suddenly the memory ran full. This happend at
>>> some step, it did not increase steadily during the whole process. Also,
>>> the CPU was at 100% from that point on. The output doesn't seem to
>>> report an error, does it?
>> It doesn't seem to report any error. I've run a valgrind on luatex with
>> the attached simple test file calling fontloader.info(); it seems to
>> have a memleak of about 80kb+(2kb per font). It's not nothing, but 2kb
>> times your 7400 fonts is about 15Mb, we're far from 3Gb... This doesn't
>> seem very easy to debug, but I'll continue to make tests about this...
>> Maybe you could run dbg or valgrind to see what's happening? (you'll
>> have to build luatex from sources if you want to follow this way, but
>> it's fairly easy).
> I'll happily do this, but unfortunately I don't even know what you are
> talking about …
> So far I've never built luatex from source, I don't know what dbg is and
> I've never heard of valgrind … is this something that can be done by a
> few lines of input that you can offer me or do I have to dig into
> building luatex? (If so, I'll try to, but it may take some time …)
> cheers
> Arno

More information about the luatex mailing list