Just meandering a bit, but that listing on the bottom rail of the application reading "Background (2.8 GB)", I assume that means that Gimp has reserved 2.8 GB of RAM for the project?
And then if I subsequently upsize the canvas to 20,000 X 20,000 that listing grows to "Background (3.4 GB)"
So, what I'm wondering....if I start out with a 16,000 X 14,000 (2.8 GB) canvas, and then put a couple hundred megabytes of content on that canvas (as well as any accompanying "undo" data Gimp maintains in the background)......and then I expand the canvas to 20,000 X 20,000 (3.4 GB) and then continue working adding more content........could I possibly be forcing Gimp's memory management into a "fragmented" state?
Similar to how one get's fragmented files on a hard drive, you know with the "flag" bit? Could it be that Gimp is being forced into some unusual acrobatics to manage fragmented memory content? (just an ignorant question, but that is what really got me started on this tangent)
And then if I subsequently upsize the canvas to 20,000 X 20,000 that listing grows to "Background (3.4 GB)"
So, what I'm wondering....if I start out with a 16,000 X 14,000 (2.8 GB) canvas, and then put a couple hundred megabytes of content on that canvas (as well as any accompanying "undo" data Gimp maintains in the background)......and then I expand the canvas to 20,000 X 20,000 (3.4 GB) and then continue working adding more content........could I possibly be forcing Gimp's memory management into a "fragmented" state?
Similar to how one get's fragmented files on a hard drive, you know with the "flag" bit? Could it be that Gimp is being forced into some unusual acrobatics to manage fragmented memory content? (just an ignorant question, but that is what really got me started on this tangent)