GIMP bomb outs anyone?

jfw

Leading Member
Messages
913
Reaction score
760
Location
US
I've been getting a lot of "GIMP has stopped working" bomb outs with GIMP 2.10.24 (rev 2). I have 2 machines: laptop with Win10, desktop with Win 8.1. Happens on both. Similar experiences anyone? Thoughts on root causes/ interventions? Thanks.
 
I've been getting a lot of "GIMP has stopped working" bomb outs with GIMP 2.10.24 (rev 2). I have 2 machines: laptop with Win10, desktop with Win 8.1. Happens on both. Similar experiences anyone? Thoughts on root causes/ interventions? Thanks.
PLease specify your workflow. Or does it crash at startup. Without specification we cannot determin what is causing those crashes.
 
The current version of Gimp (2.10.24) is very stable.

I would suggest you ask here:

Give some more details.
Where did you get your version of Gimp?
Hardware: 32 bit, 64 bit? How much RAM? In preferences, what is “Tile cache size” set to?
Workflow: How big is the image? What filters are you using? What are you doing when the problem occurs?
 
I've been getting a lot of "GIMP has stopped working" bomb outs with GIMP 2.10.24 (rev 2). I have 2 machines: laptop with Win10, desktop with Win 8.1. Happens on both. Similar experiences anyone? Thoughts on root causes/ interventions? Thanks.
PLease specify your workflow. Or does it crash at startup. Without specification we cannot determin what is causing those crashes.
Machines:
  • Laptop: Maingear Element Stage 2 , 32 GB RAM, new within last year
  • Desktop: Maingear F131 , 16 GB RAM, a few years old.
  • Both machines run C1 Pro, Office, etc. without any app faults.
  • Desktop also runs LR, PS CS6, and a bunch of other apps without any app faults.
Gimp: 2.10.24 (rev2)
  • Downloaded directly from gimp.org
  • Just the base download on the desktop (where most of the faults are occurring)
  • Base download plus G'MIC-QT on the laptop
Workflow:
  • I'm creating posters sizes 4x6" to 20x30". The "flow" is:
  • Create base background layer of desired size
  • "Open as layers" 1-8 images
  • Scale each image layer to a few inches in size, depending on overall layout
  • Position images
  • Add text
  • That's really it - nothing too sophisticated
Crashes:
  • I have had it crash immediately after startup, but rarely
  • It's crashing at random points when I'm creating the above posters
 
The current version of Gimp (2.10.24) is very stable.

I would suggest you ask here:
https://www.gimp-forum.net

Give some more details.
Where did you get your version of Gimp?
Hardware: 32 bit, 64 bit? How much RAM? In preferences, what is “Tile cache size” set to?
Workflow: How big is the image? What filters are you using? What are you doing when the problem occurs?
See post above to Toermalijn for most of the answers to your questions. Also:

Tile Cache Size:
  • Desktop: 8372154
  • Laptop: 16697826
Given all the crashes, I find it difficult to agree with your comment on stability. That said, I do manage to get my work done - I just have to save often, re-start after crashes.

Cheers
 
I've been getting a lot of "GIMP has stopped working" bomb outs with GIMP 2.10.24 (rev 2). I have 2 machines: laptop with Win10, desktop with Win 8.1. Happens on both. Similar experiences anyone? Thoughts on root causes/ interventions? Thanks.
I have not had any problems with GIMP 2.10.24, but there was a prior version--maybe like 2.10.18 or 2.10.20?--that ran fine on my Windows computer at home but crashed incessantly on my Windows computer at work. Never figured out why. I eventually uninstalled GIMP from my work computer, reinstalled the previous version, and then waited for the next version to come out--which made GIMP work fine on my work computer. All of which is a long way of saying: I've experienced a somewhat-similar issue with GIMP, but with a somewhat older version, and I have no idea why.
 
The current version of Gimp (2.10.24) is very stable.

I would suggest you ask here:
https://www.gimp-forum.net

Give some more details.
Where did you get your version of Gimp?
Hardware: 32 bit, 64 bit? How much RAM? In preferences, what is “Tile cache size” set to?
Workflow: How big is the image? What filters are you using? What are you doing when the problem occurs?
See post above to Toermalijn for most of the answers to your questions. Also:

Tile Cache Size:
  • Desktop: 8372154
  • Laptop: 16697826
Given all the crashes, I find it difficult to agree with your comment on stability. That said, I do manage to get my work done - I just have to save often, re-start after crashes.

Cheers
Your tile cache size is lower than recommended, although this advice is for Linux:

https://www.gimp.org/unix/howtos/tile_cache.html

Did you characterize the amount of memory your work requires? I'm unsure how, because I am not a Windows person. Possibly Task Manager shows memory is use by GIMP process.
 
Last edited:
The current version of Gimp (2.10.24) is very stable.

I would suggest you ask here:
https://www.gimp-forum.net

Give some more details.
Where did you get your version of Gimp?
Hardware: 32 bit, 64 bit? How much RAM? In preferences, what is “Tile cache size” set to?
Workflow: How big is the image? What filters are you using? What are you doing when the problem occurs?
See post above to Toermalijn for most of the answers to your questions. Also:

Tile Cache Size:
  • Desktop: 8372154
  • Laptop: 16697826
Given all the crashes, I find it difficult to agree with your comment on stability. That said, I do manage to get my work done - I just have to save often, re-start after crashes.

Cheers
Your tile cache size is lower than recommended, although this advice is for Linux:

https://www.gimp.org/unix/howtos/tile_cache.html

Did you characterize the amount of memory your work requires? I'm unsure how, because I am not a Windows person. Possibly Task Manager shows memory is use by GIMP process.
I can try boosting the tile cache size, but two things: (1) it's the default from the install. The installer seems to set this variable as a function of physical memory size on the target machine (empirical inference) (2) the doc says that tile cache size will affect performance, with more swaps to disk if it's too low ... ok, fine - but it shouldn't crash!
 
I've been getting a lot of "GIMP has stopped working" bomb outs with GIMP 2.10.24 (rev 2). I have 2 machines: laptop with Win10, desktop with Win 8.1. Happens on both. Similar experiences anyone? Thoughts on root causes/ interventions? Thanks.
I have not had any problems with GIMP 2.10.24, but there was a prior version--maybe like 2.10.18 or 2.10.20?--that ran fine on my Windows computer at home but crashed incessantly on my Windows computer at work. Never figured out why. I eventually uninstalled GIMP from my work computer, reinstalled the previous version, and then waited for the next version to come out--which made GIMP work fine on my work computer. All of which is a long way of saying: I've experienced a somewhat-similar issue with GIMP, but with a somewhat older version, and I have no idea why.
Ok thanks. At least I know I'm not the only one in the history of the world that has seen this issue with selected versions! :-)
 
I see you have not yet asked at www.gimp-forum.net
It is possible (or probable) that it is not a Gimp problem, but something else.

I remember one case where the problem was tracked down to a particular make and model of video card.

Another time it was other software intercepting windows events, so that events were not being returned to Gimp. The case I remember it was a third party Clipboard (which could contain multiple items). When the third party Clipboard was removed Gimp worked fine.
 
Your tile cache size is lower than recommended, although this advice is for Linux:

https://www.gimp.org/unix/howtos/tile_cache.html

Did you characterize the amount of memory your work requires? I'm unsure how, because I am not a Windows person. Possibly Task Manager shows memory is use by GIMP process.
I can try boosting the tile cache size, but two things: (1) it's the default from the install. The installer seems to set this variable as a function of physical memory size on the target machine (empirical inference) (2) the doc says that tile cache size will affect performance, with more swaps to disk if it's too low ... ok, fine - but it shouldn't crash!
Just doubled the tile cache size on the desktop... still bombed. This time it bombed while Gimp was not even the active application. Sigh...
 
I see you have not yet asked at www.gimp-forum.net
It is possible (or probable) that it is not a Gimp problem, but something else.

I remember one case where the problem was tracked down to a particular make and model of video card.

Another time it was other software intercepting windows events, so that events were not being returned to Gimp. The case I remember it was a third party Clipboard (which could contain multiple items). When the third party Clipboard was removed Gimp worked fine.
Good grief... really? I don't have any other apps that have such dependencies, nor bomb in the environment I do have. Sounds like the proverbial wild goose chase.
 
I've been getting a lot of "GIMP has stopped working" bomb outs with GIMP 2.10.24 (rev 2). I have 2 machines: laptop with Win10, desktop with Win 8.1. Happens on both. Similar experiences anyone? Thoughts on root causes/ interventions? Thanks.
May be a problem with old drivers etc. The simplest way to check I know is with CCleaner. Download and acrivate trial. Works for 14 days if you dont want to purchase it.

I did that and it found 26 outdatet drivers. After going trough with updates my PC was in fact a lot better and no more crashes.
 

Keyboard shortcuts

Back
Top