| Summary: | fontconfig cache creation takes a long time during GIMP startup | ||
|---|---|---|---|
| Product: | fontconfig | Reporter: | Michael Schumacher <schumaml> |
| Component: | library | Assignee: | fontconfig-bugs |
| Status: | RESOLVED MOVED | QA Contact: | Behdad Esfahbod <freedesktop> |
| Severity: | normal | ||
| Priority: | medium | CC: | akira, dr.khaled.hosny, eduard.braun2, freedesktop |
| Version: | unspecified | ||
| Hardware: | Other | ||
| OS: | Windows (All) | ||
| See Also: |
https://bugzilla.gnome.org/show_bug.cgi?id=782676 https://bugs.freedesktop.org/show_bug.cgi?id=99360 |
||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
|
Description
Michael Schumacher
2017-07-17 12:06:34 UTC
what version of fontconfig did gimp 2.8.22 use? Likely some 2.11, judging by the 2014 creation date of the libfontconfig dll file (which is most likely taken from opensuse's mingw repository. 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 Aha. then what I can propose is to try the latest one. it might be already fixed in there. The slowness at the first time is intentional and not a bug in fontconfig at all. usually it is avoidable on most distributions by generating caches on installation time. but it often happens on Windows because that necessary process isn't usually taken. I'm not familiar with Windows though, if there are any trigger on installing fonts, you could do run fc-cache on it or run fc-cache by timer periodically if the cache location is on the common place. For first-time slowness, let's follow up here: https://bugs.freedesktop.org/show_bug.cgi?id=64766#c47 -- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/fontconfig/fontconfig/issues/58. |
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.