37

Is there any way to speed up GIMP's startup time on Windows Vista Home Premium 32-Bit 1.6 [Dual] Intel Processors? On XP [different computer], it loads in less than 3 seconds. On Vista, it takes 20 seconds:

  • 2 Seconds (other - fonts, brushes, etc)
  • 18 Seconds (extension-script-fu)

It just freezes at extension-script-fu. Looking at Process Explorer, I see that it's not taking any CPU at all. EDIT 1: It does seem to be taking 50% of the CPU.

It gets stuck for about 18 seconds, and then starts working again. Then, the actual GIMP program pops up [...finally]. I have the latest stable version running (I think). I tried it with XP SP2 Compatibiliy mode and/or Run As Administrator, but that didn't help.

EDIT 2: One way would be to disable script-fu. Does anyone know how to disable it at startup? Is it possible? Would GIMP still work? What wouldn't work? Could I start it later, after loading?

EDIT 3: Seems to startup at lightning speeds even with script-fu (<3 seconds) in GIMP 2.8 RC1 on Windows Vista.

Mateen Ulhaq
  • 3,452
  • 6
  • 35
  • 56
  • It takes about 20 or more seconds to run on my PC, and it's WinXP SP3. Not real happy about that either. – Steve Jan 28 '11 at 08:13
  • 4
    @Steve They really should fix it. But of course, when I asked at a GIMP forum once, they started telling me how impatient I was... They said they'd be happy if it took even 2 minutes to load! (Probably because they have nothing else to do.) – Mateen Ulhaq Jan 29 '11 at 04:57
  • As far as I know, the only real way to speed up gimp startup, is having a very fast pc. On my core i5, it loads about 3secs. – Michael K Feb 16 '11 at 09:50
  • 1
    @Michael The problem is that the GIMP process stops using CPU for 18 seconds. So, it's not really a problem with how fast my PC is (Intel Core 2 Duo @ 1.8Ghz/processor), or how much RAM it's got (2GB, have my Vista lean and mean, removed unnecessary services/security risks, disabled Aero, etc; Also, I have ReadyBoost with a Kingston DataTraveller USB 2.0 with 4GB of space.) – Mateen Ulhaq Feb 18 '11 at 00:35
  • This is kinda strange, like I said, on my computer it loads fast. There might be a compatibility problem with windows vista. – Michael K Feb 18 '11 at 09:13
  • 1
    @muntoo: the majority of program load times (not just GIMP) is not spent on the CPU, the majority of program loading time is spent reading from harddisk. A harddisk read speed highly depends on how fragmented the drive is, sequential reading typically can reach 40MB/s, but highly random reads can kill performance reaching below 1MB/s. A program that needs to load 100 MB of data can be loaded in 2-3 secs if the read is mainly sequential, but it can take more than 20 secs if the files are scattered about. – Lie Ryan Sep 04 '11 at 19:10
  • @muntoo: having a large RAM can masks hot loading time (i.e. reloading just after you closed it) since the program can be loaded from harddisk cache in the RAM. But ultimately, it's the harddisk reading speed that is the true bottleneck of loading time. Making sure your system is well defragged, and GIMP's files are *physically close together in the harddisk plate*; and that the harddisk is not too full (having lots of empty space generally leads to less fragmentation), generally would help with slow loading times. – Lie Ryan Sep 04 '11 at 19:29
  • Year 2023 and the problem continues: GIMP 2.10.20 and on my machine it takes forever while showing "looking for fonts". For work reasons I have many fonts on my machine. But: I hardly ever need to put any text into any bitmap, because I would use Scribus for documents with bitmaps and text, rather than use GIMP. So I would like an option where it never looks for fonts during start-up and only starts looking if I ever need to put text (maybe twice per year) directly into a screenshot, where quality never matters. Also in those cases the font does not matter either. – Martin Zaske Jan 11 '23 at 17:28

9 Answers9

29

If this happens to you when the splash screen gets to "Loading Data Files - Fonts", then there are several workarounds to this slowdown.

To analyze the slowdown, you may add the --verbose parameter to GIMP to better analyze startup problems.

The article Slow GIMP startup : Graphics advises :

This used to happen to me too. Some kind-soul told me that there in the c:\documents and settings\user-name\ directory, there will be a ..fonts-cache1 file. Delete that cache and re-start GIMP. First time it takes a while to make that fonts-cache again, but from 2nd time it should be pretty normal.

Note that on newer systems (Windows 7 & 10) this folder moved to C:\Users\<username>\AppData\Local\fontconfig. A quick way to get there is typing: Win+r, and entering %appdata%/../local/fontconfig (or write the same in the address line of a file-explorer window).

Another advise is :

I created a shortcut with the command parameter --no-fonts and it started very quickly.

The GIMP FAQ says :

The GIMP takes too long to load - how can I speed it up?

The main things are to make sure you are running at least version 1.0, and make sure you compiled with optimization on, debugging turned off, and the shared memory and X shared memory options tuned on.

Or, buy a faster system with more memory. 8^)

If it's still too slow for you, the easiest speedup is to invoke the GIMP with the "--no-data" option. This prevents the GIMP from loading patterns, brushes, and similar resources when it starts. You may benefit slightly from the "--no-splash" option as well; you might want to time that one to see if it really helps enough to be worthwhile.

If the problem lies in one or more extensions, the only solution is to uninstall these extensions. The extensions are found in the folder GIMP is installed in (usually Program Files), inside C:\Program Files\GIMP-2.0\lib\gimp\<version>\plug-ins. Just rename the extension file to .old or something, for example script-fu.exe to script-fu.exe.old. The easiest way to get rid of all the extensions is to rename the entire plug-ins folder.

exhuma
  • 1,127
  • 1
  • 11
  • 24
harrymc
  • 455,459
  • 31
  • 526
  • 924
  • 1
    I tried them, but they don't help. (And advice #1 is not applicable - no such file exists.) – Mateen Ulhaq Feb 17 '11 at 00:12
  • What stage in the startup process takes the longest time? – harrymc Feb 17 '11 at 07:05
  • Note: I have GIMP and I have found the file `C:\Users\\.fonts.cache-1`. It is rather large and not even hidden. – harrymc Feb 17 '11 at 09:07
  • @harrymc The `extension-script-fu` takes 18 seconds. – Mateen Ulhaq Feb 18 '11 at 03:34
  • I have added some more info. – harrymc Feb 18 '11 at 06:43
  • 2
    @harrymc Renaming it works - 5 seconds. :) When I try running script-fu.exe (just for fun), I get: "*script-fu.exe - Unable To Locate Component --------------------------- This application has failed to start because libgimpui-2.0-0.dll was not found. Re-installing the application may fix this problem.*" Not sure if it means anything, just sayin'. – Mateen Ulhaq Feb 22 '11 at 06:50
  • 2
    script-fu is probably launched from The GIMP with a certain environment that you don't have. Now that you know the exact cause, you could maybe start a discussion on their forums, so maybe the problem will be fixed with a future version. – harrymc Feb 22 '11 at 07:01
  • *`fonts-cache` file doesn't exist on my system. – user198350 Dec 06 '17 at 17:41
  • @user598527: This answer dates from 2011. – harrymc Dec 07 '17 at 11:47
  • The other points are relevant, `--no-fonts` parameter reduced the startup time to approximately 10%! – user198350 Dec 07 '17 at 12:35
  • 1
    This answer helped me, but to get specific for Windows 10, Gimp 2.8: with Gimp closed delete the font cache located at `C:\Users\\AppData\Local\fontconfig\cache`. Start Gimp, and it will rebuild the cache; subsequent Gimp startups will be fast. My Gimp startup time went from >2 minutes down to <10 seconds. – dhobbs Jan 18 '18 at 17:47
  • In my case I need to have many fonts on my machine. But I never need them in GIMP. Here the no-fonts option made the real difference. Thank you muchly for this answer. – Martin Zaske Jan 11 '23 at 17:38
7

Selected answer worked for me.

However, had to use different steps.

Using Windows 7
Using Gimp 2.8

=== Step 1.   Diagnose ===

  1. Navigate to C:\Program Files\GIMP 2\bin
  2. Shift + Right Click -> "Open Command Window Here"
    (click the empty space of the folder, not an icon)
  3. Type gimp-2.8.exe --verbose
  4. Watch the Gimp console that pops up :
    see what is taking the longest to load.

Gimp console pic -- hanging on "Loading fonts"

For me, it would hang on "Loading fonts" for 15 seconds,
every single time I launched.

  1. For a quick process of elimination :
    close Gimp + type this into Windows Command Prompt

    gimp-2.8.exe --verbose --no-fonts


n o t e :
calling gimp-2.8.exe only works if your console's path
is the same as the gimp-2.8.exe directory.


=== Step 2.   Locate Gimp's font cache ===

C:\Users\User_Name\ had no files resembling ".fonts-cache1"
C:\Users\User_name\.gimp-2.8 had nothing font related except an empty fonts folder

If you do find it there : follow the steps of the selected answer above.

On my machine :
the font folder where Gimp 2.8 stores its font cache
is located in : C:\Users\User_Name\AppData\Local\fontconfig

    h i n t :
    click Windows start button, type %appdata%/../local then press enter


=== Step 3.   Verify this is the right folder ===

Inside of C:\Users\User_Name\AppData\Local\fontconfig
there should be a folder called cache.
Rename it to anything else : example cache.backup .

  1. Stay in the ..\AppData\Local\fontconfig directory.
  2. Run Gimp.
  3. See if it generates a new cache folder.

If so, you definitely know that this is Gimp's font cache folder.


=== Step 4.   Hopefully it's fixed; let's find out ===

The last step hid Gimp's cache,
and Gimp regenerated a new one.

If you close Gimp + reopen it,
it should open significantly faster
(hopefully this was the root of your problem!)

Grass H0PEr
  • 79
  • 1
  • 4
  • For the 2.9 development version (and possibly 2.10 on release?) it seems to be using `C:\Users\User_Name\.cache\fontconfig` – GreenReaper Jan 01 '18 at 14:08
  • Working solution with same steps using Windows 10. Thanks a lot! – Metafaniel Feb 13 '18 at 18:15
  • 1
    Instead of adding a new answer (which is essentially the same as the accepted one) you should have proposed a change on that one with the new folder-name. This would improve visibility of the solution. – exhuma Nov 18 '18 at 16:16
4

I copied all files in C:\Program Files\GIMP 2\lib\gimp\2.0\plug-ins to a new folder named Unused, also inside plug-ins.

Started up Gimp: ~1 second compared to ~40 seconds previously. I then copied frequently used ".exes" into the plug-ins folder. Now Gimp starts in ~3 seconds.

Arjan
  • 30,974
  • 14
  • 75
  • 112
SAm
  • 161
  • 4
  • Welcome to Super User! But... don't you see the preview, or the result? And why need those arrows anyway? @Martin did a good job, but that still [looked horrible on mobile](http://i.stack.imgur.com/1DAsU.png). And it's still useless to add the arrows. Please see also [Other people can edit my posts?!](http://superuser.com/faq#editing) Thanks. – Arjan May 19 '13 at 11:11
2

In my experience Windows Vista is notoriously slow with less than 4 GBs of RAM (and you mentioned that you have 2 GBs). Switching to Windows XP improves things greatly but the drivers aren't always available with newer hardware so the next best option is to go for Windows 7 (which also seems to need a lot of RAM, unlike XP).

I have also noticed on some computers that the Disk Defragmentation schedule doesn't run in Vista despite being scheduled to run weekly, so you may wish to try running this manually -- the "Disk Defragmenter" should be in your Start Menu under "Accessories" -> "System Tools." After running this twice, I find that things speed up considerably (although it never seems to be as good as new).

An in-depth comparison of various Disk Defragmentation tools can be found here, by a Mr. Roedy Green who is amazingly detailed and has a very high level of technical expertise, but also is very good at explaining things in an easy-to-understand fashion: http://mindprod.com/jgloss/defragger.html

Disk Defragmentation is probably your best bet if you can't switch to a better OS.

Randolf Richardson
  • 14,634
  • 39
  • 52
  • I use Auslogics DiskDefrag + Defraggler, and as I've said in the comments below, I've gotten my Vista tweaked as hard as possible while still looking prettier than XP (disabling Aero). I've heard of Vistas where GIMP comes on fast (3 seconds), and on XP it doesn't. On "my" XP (laptop), it comes on fast, on Vista, it doesn't... BTW, my machine is *better* than when it came all "new" and "shiny". – Mateen Ulhaq Feb 18 '11 at 05:30
2

The issue is quite likely your brushes or plugins. For example, GIMP loads all brushes into memory as it's starting up. On my own system, this consumes roughly 1.1 GB of RAM, and it does this before loading the splash screen image (the splash screen window is there, but with a blank white background). Once the program has finished consuming 1.1 GB of RAM, the image appears and it loads up rather quickly. If I delete my brushes, the program starts up in about 4 seconds and consumes only 49 MB of RAM.

Edit: Windows 7 64-bit, Pentium Dual-Core 2.7 GHz, 4GB RAM. GIMP 2.8 from Partha's Place.

Ryan Fitzgerald
  • 21
  • 1
1

I have experienced this very thing (except on a mac) and I figured it was another weird mac issue that I just had to put up with. I was waiting far longer than 20 seconds at extension-script-fu. The issue for me was that I had a removable USB storage device (16 GB and not too speedy) and my machine appeared to be maintaining an index of files on that drive.

When I disabled the file indexing for that device, this whole issue disappeared. Not sure that really helps, and I don't know how to do that in windows but maybe something similar. (I don't have GIMP on my windows machine)

Sathyajith Bhat
  • 61,504
  • 38
  • 179
  • 264
user568417
  • 11
  • 1
1

Font processing is often a cause of slow Gimp startup. There seem to be many sources of the problem, and suggested solutions may not work. In Gimp 2.6 on Windows, I found that the "--no-fonts" command line parameter did work (saving 50 sec), but (1) you then cannot add text to an image, and (2) you have to pre-start Gimp rather than just clicking on an image.

An odd but effective solution I found was to go to Edit-->Preferences-->Folders-->Fonts and delete the entry there (normally ".gimp-2.6\fonts"). This has the effect (for unobvious reasons) of eliminating the font startup delay but still allowing text usage on images using all the fonts installed in Windows.

mgkrebbs
  • 294
  • 3
  • 12
  • I did this and it does not have the effect of eliminating font startup delay for me. Gimp is still "looking for fonts" for half a minute on startup. – comodoro Aug 03 '17 at 08:55
0

Gimp takes around 10 seconds to start here, on a approx 2 GHz Xeon, Arch Linux. This tells me it's most likely to be a problem with the Windows-version of Gimp. Also, I've experienced myself that the Windows-version of Gimp takes a long time to load.

To answer your question, you could run Linux. I bet Gimp would even start up faster if you run Gimp in Linux in a virtual machine (like VirtualBox).

Alexander
  • 287
  • 3
  • 10
0

Other good way is to move extra brushes from BRUSHES folder to "BRUSHES_BACKUP" folder...

Some other tips:
1) http://www.ehow.com/how_8385516_make-gimp-load-faster.html
2) http://fooit.blogspot.com/2011/03/gimp-startup-too-slow-for-you-here-are.html

T.Todua
  • 3,815
  • 9
  • 42
  • 57