[Fontconfig-bugs] [Bug 101820] fontconfig cache creation takes a long time during GIMP startup

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=101820

--- Comment #3 from Eduard Braun <eduard.braun2 at gmx.de> ---
We have exactly the same problem in Inkscape for Windows.

We could resolve one issue we faced [1]:
By default fontconfig stored the cache to a temporary location. If this
temporary location was cleared (i.e. by some system cleanup tool) the cache had
to be re-created the next time Inkscape was run. (Maybe something like this is
causing some of the "every time" comments for you?)
We fixed the issue by configuring fontcache to write the cache to
LOCAL_APPDATA_FONTCONFIG_CACHE

We still have the underlying issue [2]:
Creation of the fontconfig cache needs time, especially on slower systems or
systems with a lot of fonts installed. This delays the startup of Inkscape
considerably, which is especially bad since it obviously affects every first
time user (and even worse because Inkscape - in contrast to GIMP - does not
have a startup screen informing the user about what it's doing.

Subsequent startups with this configuration are usually fast though, with the
exception of bug 99360 which lately prevented fontconfig to update an outdated
cache file. The behavior matches what you experience: a .new file with the
updated cache was created but never used to actually replace the old cache
(this was due to file locks as described in the linked bug; the patch there
fixed the issue for us, though).


[1] https://bugs.launchpad.net/inkscape/+bug/1196373
[2] https://bugs.launchpad.net/inkscape/+bug/1528629

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/fontconfig-bugs/attachments/20170718/e5d4202c/attachment-0001.html>