GNOME Bugzilla – Bug 559550
[fontconfig] Does too much work during startup
Last modified: 2008-11-06 03:45:09 UTC
My own bad. Logging here for the record. Currently we do a cache check when starting up. That's stupid as fontconfig implicitly initalizes itself, then immediately stat everyone again to see if cache is up to date. What we want instead is to explicitly initialize fontconfig to do any recaching as needed. Patch coming.
Fixed. 2008-11-05 Behdad Esfahbod <behdad@gnome.org> * plugins/xsettings/fontconfig-monitor.c (fontconfig_cache_init): * plugins/xsettings/fontconfig-monitor.h: * plugins/xsettings/gsd-xsettings-manager.c (start_fontconfig_monitor): Only initialize fontconfig when starting up. A cache update is redundant there. (bug #559550)
Created attachment 122074 [details] [review] The patch