06-21-2017, 10:06 AM
(This post was last modified: 06-21-2017, 10:20 AM by rich2005.
Edit Reason: edit
)
(06-21-2017, 08:11 AM)Ofnuts Wrote: thing to check is whether the font cache has been created (somewhere in the user's AppData IIRC).
@ Ofnuts, This is the font cache on my Win 7 VM C:\Users\your-name\Appdata\Local\fontconfig\cache
What advice? Delete it? Gimp will make another, presumably other applications will if required. Should be safe enough.
I do wish MS Win would not make it so easy to install fonts system wide.
In theory, fonts can be disabled so that they do not appear in applications. That does not work for me and this Gimp installation. Might work if the cache is deleted. I will try that later. (Edit: hidden fonts still showing in Gimp, so that is no good. Back to removing fonts)
Some statistics for comparison. This is that Win7 64 bit VM with a very modest 2 GB memory allocation.
Starting a very basic Gimp, no extra fonts. 4 to 12 seconds (quicker time if you have already run Gimp that session)
Using the -f switch for no fonts. Not much difference 4 to 8 seconds.
After installing into Windows 130 fonts
First run, Gimp 30 seconds - presumably creating the cache file.
Second run, Gimp down to about 15 seconds.
Using the -f switch for no fonts, about 8 seconds
So if you get times much greater than that, probably a broken font.
The font cache now looks like this. Delete that last entry? but with a broken font AFAIK you still have the problem. Looks like deleting the excess fonts is the option.