That's what is so maddening about it. It'll woo you in with a false sense of security, dozens of flawless operations. And then suddenly when you least expect it...*poof*
I lost 6 hours of work on one such instance a few days ago (only myself to blame, but I was still livid)......so I started saving in incremental steps, just to be proactive. And in one such instance yesterday I had about 3 hours of work in progress, was just about to plot a tiny little path, and thought "whoops, you better save first just in case" so I saved a worktemp.xcf just out of caution, and sure enough on the very next step as I plotted the tiny little path, everything went *poof* and I felt so vindicated for having thought to save first.
It's really rare that I have Gimp either seize up or go "poof", and that is reflecting upon years of use.
Which makes my experiences this past week, and particularly yesterday, all the more note worthy...I was beside myself in negative awe.....wondering what had gone south.
FWIW it was a 126 MB XCF file that ultimately exported as a 65 MB PNG, and as a 28 MB GIF, and as a 20 MB JPG ..... the finished work being a composite of numerous 4000 X 2000 "tiles" each approx 5 MB in size.
And there was just something about my expanding the canvas from 16,000 x 11,000, to 16,000 x 14,000 that made work performed after the enlargement especially precarious.
Bear in mind, this is not a "complaint" per se...just an observation made particularly relevant after coming here and reading this thread title....
Just as a benchmark, plotting the following path, 224 pixels wide, took 28 seconds before the results were painted on the canvas. I could have been performing other tasks on my PC at the time, but Gimp itself was pretty much preoccupied with the procedure (FWIW)
![[Image: Q7KCD3t.png]](https://i.imgur.com/Q7KCD3t.png)
I lost 6 hours of work on one such instance a few days ago (only myself to blame, but I was still livid)......so I started saving in incremental steps, just to be proactive. And in one such instance yesterday I had about 3 hours of work in progress, was just about to plot a tiny little path, and thought "whoops, you better save first just in case" so I saved a worktemp.xcf just out of caution, and sure enough on the very next step as I plotted the tiny little path, everything went *poof* and I felt so vindicated for having thought to save first.
It's really rare that I have Gimp either seize up or go "poof", and that is reflecting upon years of use.
Which makes my experiences this past week, and particularly yesterday, all the more note worthy...I was beside myself in negative awe.....wondering what had gone south.
FWIW it was a 126 MB XCF file that ultimately exported as a 65 MB PNG, and as a 28 MB GIF, and as a 20 MB JPG ..... the finished work being a composite of numerous 4000 X 2000 "tiles" each approx 5 MB in size.
And there was just something about my expanding the canvas from 16,000 x 11,000, to 16,000 x 14,000 that made work performed after the enlargement especially precarious.
Bear in mind, this is not a "complaint" per se...just an observation made particularly relevant after coming here and reading this thread title....
Just as a benchmark, plotting the following path, 224 pixels wide, took 28 seconds before the results were painted on the canvas. I could have been performing other tasks on my PC at the time, but Gimp itself was pretty much preoccupied with the procedure (FWIW)